9 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Courier Imap + NF...
FromSent OnAttachments
Pavel GeorgievNov 26, 2007 7:35 am.log
Jose CelestinoNov 26, 2007 8:19 am 
Gordon MessmerNov 26, 2007 9:23 am 
Pavel GeorgievNov 26, 2007 10:15 am 
Gordon MessmerNov 26, 2007 10:29 am 
Pavel GeorgievNov 26, 2007 10:48 am 
Pavel GeorgievNov 27, 2007 9:42 am 
Pavel GeorgievNov 30, 2007 1:15 pm 
Sam VarshavchikNov 30, 2007 3:16 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Courier Imap + NFS mailboxesActions...
From:Gordon Messmer (yiny@eburg.com)
Date:Nov 26, 2007 9:23:06 am
List:net.sourceforge.lists.courier-users

Pavel Georgiev wrote:

To eliminate nfs race conditions I`ve turned the second mail server off, so there is only one nfs client accessing the mailboxes. The nfs server is a linux box as well, running Ubuntu 7.04, the underlying fs is reiserfs and it runs on top of drbd (if this makes any differance).

It *shouldn't*, but I wouldn't be surprised if it did. I've never seen that behavior. What I'd do is get a packet capture of the traffic between the IMAP server and the NFS server, and analyze it with ethereal. You can capture the packets with tcpdump from either host:

imap# tcpdump -s0 -o /tmp/nfs.chatter host <nfs hostname>

Start the dump before you log in to IMAP, and stop it with ctrl+c a few seconds after you've logged in. You should be able to use ethereal to check whether or not the NFS server is reporting those files in new/ after they've been moved. If you're not sure how to do it, you can send me the packet capture and I'll help you figure it out.