In use as filesystem locked? maybe created by NFS server?

If dovecot died then the temporary file is permanent.

2010/10/7 Marcus Rueckert <darix@opensu.se>:

On 2010-10-07 12:53:45 +0200, Antonio Perez-Aranda wrote:

...

I'm using dovecot-1.2.15 and NFS as storage of Maildir . When I try over IMAP and Evolution to move a mail to another Imap Folder, a file like .nfs000000000159816c0000245 is created and when move operation is finished, the file is deleted.

Sometimes, this file isn't deleted and then, you can see a new imap folder called .nfs000000000159816c0000245 when you restart your Evolution or another Imap Client.

Is this file created by dovecot? maybe, must dovecot delete this file on login?

I think thats is easy fix this with a Post-Login script but I think that dovecot must delete it

those files/directories are created when you try to delete a file/directory on nfs, but it is still in use.

   darix

-- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org

On Fri, Oct 8, 2010 at 6:15 AM, Ed W <lists@wildgooses.com> wrote:

...

Sometimes, this file isn't deleted and then, you can see a new imap folder called .nfs000000000159816c0000245 when you restart your Evolution or another Imap Client.

Something of a workaround, but there is an option to stat each file starting with a . and determing if it's directory or a file.  This would at least prevent the temp file appearing as a folder (at the cost of more disk io)

Perhaps a good feature request from us NFS+maildir users would be for dovecot to ignore anything like .nfs[0-9]{20,} (or other nfs silly file patterns, if there are any), since there's almost no way someone's really got a folder called that. Presumably that'd be too expensive to do on every single file, but I'm guessing relatively painless to do on the top-level directory, when dovecot is building the list of IMAP folders, esp versus having to stat() them all.

Ok, it'll break *one* guy somewhere, probably an exec :)