On Monday 08 December 2003 13:29, 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:
>
>
> #!/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.
>
> Is there anything I can do to get this bug fixed?
>
At testlab run this test script and not found this bug in freevps-1.1.0.
======
[EMAIL PROTECTED] root]# ./testnfs.pl
Testing fcntl...
[EMAIL PROTECTED] root]#
cat locktest.lock
[EMAIL PROTECTED] root]#
=======
after it share work correctly - dir can been changed and files been read.for test share do mounting inside vps. -- With best regards, Alex _______________________________________________ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
