From: Jan Zuchhold (Jan_at_Zuchhold.com)
Date: Mon 08 Dec 2003 - 12:22:46 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
> > fileserver:/home /var/lib/vservers/$2/home
> > Script to reproduce error:
> > #!/usr/bin/perl
> > 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.
2.4.22ctx-17c: works, no problem
2.4.22-vs1.00: does not work, fcntl broken
2.4.23-vs1.20: does not work, fcntl broken
> 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
yep, i just checked, i used exactly the same config for 2.4.22-vs1.00 and
> I will try to reproduce ...
> there should be no difference in behaviour between
> 2.4.22ctx-17c and vs1.00 ...
Well, maybe it should, but it isn't ;)
Vserver mailing list