From: Jan Zuchhold (Jan_at_Zuchhold.com)
Date: Mon 08 Dec 2003 - 11:29:31 GMT
I just tested vs1.20 and it appears that fcntl locking on NFS shares mounted
inside a vserver is still broken, as I reported some time ago (04.11.2003). I
quote from my other posts:
The share is mounted like this in the vserver startup script:
/usr/sbin/chbind --ip 192.168.1.145 --bcast 192.168.1.255 mount -t nfs
Script to reproduce error:
open FH, ">locktest.lock" or die "Cannot open $fn: $!";
print "Testing fcntl...\n";
@list = (F_WRLCK,0,0,0,0); # exclusive write lock, entire file
$struct = pack("SSLLL",@list);
fcntl(FH,&F_SETLKW,$struct) or die("cannot lock because: $!\n");
# With vs1.00 and vs1.20 I don't get here
print FH "blabla";
Symptoms: NFS Share stops responding, all processes go to state D.
Because of this problem nearly all of my machines are stuck at 2.4.22ctx-17c.
Is there anything I can do to get this bug fixed?
Vserver mailing list