From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Mon 08 Dec 2003 - 12:02:44 GMT
On Mon, Dec 08, 2003 at 12:29:31PM +0100, Jan Zuchhold wrote:
> Hello List!
> 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
> fileserver:/home /var/lib/vservers/$2/home
> Script to reproduce error:
> use Fcntl;
> 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";
> close FH;
> 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.
hmm, so this _is_ working with 2.4.22ctx-17c?
which patch of vs1.20 did you try, the one for 2.4.22
and the 2.4.22 source or the one for 2.4.23?
did you use the _same_ config file as for the
did 2.4.22-vs1.00 work for you?
> Is there anything I can do to get this bug fixed?
if you used the 2.4.23, could you try with 2.4.22+patch
and if this works, 2.4.23 without patch?
could you try 2.4.22-vs1.00 with the same config as
2.4.22ctx-17c, and see if it works?
I will try to reproduce ...
there should be no difference in behaviour between
2.4.22ctx-17c and vs1.00 ...
> Thank you,
> Vserver mailing list
Vserver mailing list