On Jan 25, 2007, at 1:02 PM, Ben Rockwood wrote:
Robert Milkowski wrote:CLSNL> but if I click, say E, it has F's contents, F has Gs contents, and no CLSNL> mail has D's contents that I can see. But the list in the mailCLSNL> client list view is correct. I don't belive it's a problem with nfs/zfs server.Please try with simple dtrace script to see (or even truss) what files your imapd actually opens when you click E - I don't belive it opens Eand you get F contents, I would bet it opens F.I completely agree with Robert. I'd personally suggest 'truss' to start because its trivial to use, then start using DTrace to further hone down the problem.In the case of Courier-IMAP the best way to go about it would be to truss the parent (courierlogger, which calls courierlogin and ultimately imapd) using 'truss -f -p <PID>'. Then open the mailbox and watch those stat's and open's closely.I'll be very interested in your findings. We use Courier on NFS/ ZFS heavily and I'm thankful to report having no such problems.
Thanks for all the help. It turned out to only be tangentially related :-) to nfs and not at all really to zfs. And not a caching issue.
courier-imap keeps a uid database file for helping it and in the affected maildirs it couldn't update that due to bad permissions on the main maildir (subdirs where maildir stores stuff were correct). Since those are inherited on the nfs client from the server I updated the permissions on the nfs server and all is well.
Thanks Chad
benr.
--- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
