Anyone who has NFS, could you test: http://dovecot.org/tmp/locktest.c 1. Compile: gcc locktest.c -o locktest -Wall -g 2. Start in server 1: ./locktest temp1 3. Start in server 2: ./locktest temp2 4. Server 1 might log "unlink() failed" error after starting the second locktest, ignore that. It starts writing something like: 1 successes 12 successes link() succeeded, but link count=1 12 successes What I'd like to know is what OS you use on your NFS clients, what NFS server you use and what errors does it give (errors being those "link() succeeded/failed, but .." messages). I'm getting that "link() succeeded, but link count=1" error with FreeBSD 6.2. So I'd like to know if this is a FreeBSD bug, NFS server bug or a more common NFS problem that I should work around.. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20071115/7c554dc8/attachment-0002.bin>
On Thu, 2007-11-15 at 04:32 +0200, Timo Sirainen wrote:> Anyone who has NFS, could you test: http://dovecot.org/tmp/locktest.c(did a minor update to that in case someone already got it)> What I'd like to know is what OS you use on your NFS clients, what NFS > server you use and what errors does it give (errors being those "link() > succeeded/failed, but .." messages).Linux doesn't seem to give any errors. So I guess it really is a bug and not a general problem. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20071115/faf51e4b/attachment-0002.bin>
On Thu, 15.11.2007 at 04:32:16 +0200, Timo Sirainen wrote:> Anyone who has NFS, could you test: http://dovecot.org/tmp/locktest.c > > 1. Compile: gcc locktest.c -o locktest -Wall -g > 2. Start in server 1: ./locktest temp1 > 3. Start in server 2: ./locktest temp2 > 4. Server 1 might log "unlink() failed" error after starting the second > locktest, ignore that.I'm not quite sure how this is all meant. What's the point in running this on two different NFS servers? Do you mean to run it on two clients, inside the same NFS dir using the same 'temp' ressource? I ran it on a 6.2 FreeBSD Server and a 7.0 FreeBSD client. When using 'temp1' and 'temp2' as per your example, nothing really breaks. When using 'temp1' for both, I got this on the 7.0 client: % /tmp/locktest temp1 6 successes 14 successes 23 successes 33 successes unlink(): No such file or directory 42 successes 42 successes 42 successes 43 successes 43 successes 43 successes link(): No such file or directory (1)%> It starts writing something like: > > 1 successes > 12 successes > link() succeeded, but link count=1 > 12 successesThis never happened. Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt.
Hi Timo,> I'm getting that "link() succeeded, but link count=1" error with FreeBSD > 6.2. So I'd like to know if this is a FreeBSD bug, NFS server bug or a > more common NFS problem that I should work around..Same here, im getting that error on FreeBSD 6.2. Cor