Hello, I'm testing version 1.1.12 and occasionally there is Mar 18 14:40:44 imap2 dovecot: [ID 107833 mail.error] IMAP(xyz): nfs_flush_file_handle_cache_dir: rmdir(/home/xyz) failed: Device busy It seems that it is related to a crash of the previous imap process of that user. And it doesn't seem to cause any problems. So can it safely be ignored ? It is on Solaris 10. Index storage is local (UFS) and mailbox storage is NFS (mail_nfs_storage=yes). Martin --------------------------------------------------------------- Martin Preen, Universit?t Freiburg, Institut f?r Informatik Georges-Koehler-Allee 52, Raum 00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 preen at informatik.uni-freiburg.de fax: ++49 761 203-8242 www.informatik.uni-freiburg.de
On Wed, 2009-03-18 at 16:42 +0100, Martin Preen wrote:> Hello, > I'm testing version 1.1.12 and occasionally there is > > Mar 18 14:40:44 imap2 dovecot: [ID 107833 mail.error] IMAP(xyz): > nfs_flush_file_handle_cache_dir: rmdir(/home/xyz) failed: Device busy > > It seems that it is related to a crash of the previous imap process > of that user. And it doesn't seem to cause any problems. So can it > safely be ignored ?Yes, you can ignore it, although it means that Dovecot couldn't flush file handle cache. So if there are multiple servers accessing the same mbox at the same time you might have locking timeouts due to the OS caching the existence of the dotlock. I guess /home/xyz is actually the mountpoint? That's the reason it gives the EBUSY. Mails are typically stored in a directory that's not a mountpoint and this error doesn't happen then. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20090318/bfb13044/attachment-0002.bin>