[Dovecot] deliver and stale NFS file handles

Christoph Berkemeier christop at physik.tu-berlin.de
Sat Oct 17 11:52:50 EEST 2009


Timo Sirainen schrieb:
> On Fri, 2009-10-16 at 14:25 +0200, Leon Meßner wrote:
>> Oct 16 00:10:42 mail3 dovecot: deliver(user):
>> write_full(/home/r/user/.temp.backupmail.22774.d17050a07b2108e8)
>> failed: Stale NFS file handle
>>
>> It nearly never happens with text/plain mails but _very_
>> often when mails have attachments of some different type. This is inside
>> a 7.2-RELEASE-p2 FreeBSD jail. The NFS export is mounted from the
>> machine that is running the jail. Locking with lockf works.
> 
> It happens with mails that are larger than 128 kB. Then Dovecot creates
> a .temp.* file and unlink()s it and tries to keep using it as a
> temporary file. I thought this would have worked with all NFS clients,
> since at least Linux then renames the file to .nfs.* file and deletes it
> automatically..
> 
> Can you try what happens if you do in your FreeBSD on NFS system:
> 
> touch foo
> tail -f foo&
> rm -f foo
> fg
> 
> Does it complain about stale NFS handle?

Yes, it does complain: "tail: (null): Stale NFS file handle"
I tried the same on /tmp, which is based on UFS, and it worked. Do you
think this is a new FreeBSD bug? And if so, are you going to report it?


MfG
	Christoph

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 898 bytes
Desc: OpenPGP digital signature
Url : http://dovecot.org/pipermail/dovecot/attachments/20091017/414e0e3a/attachment.bin 


More information about the dovecot mailing list