> Because I am getting crazy with nfs, I did following tests and the results
> are out of my understanding:
>
> I tried the next fcntl function in different nfs clients:
>
> fcntl(fd, F_SETLK, &fl struct..) where l_type= F_RDLCK
>
> and I've got the following results in a file which was stored in a nfs
> server (2.0.36).
>
> - In the original server, OK.
> - In a 2.0.36 nfs client, OK.
> - In a 2.2.1 client, BAD!!!!????
>
> The three machines have user space nfsd v2.2b37
I'm getting something like this... I can't lock files on NFS partitions :
fcntl(3, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = -1 ENOLCK (No locks available)
Running through the debug output from the kernel I get :
Mar 4 00:18:23 thagdal kernel: nsm_mon_unmon: rpc failed, status=-93
Mar 4 00:18:23 thagdal kernel: lockd: failed to monitor 194.42.226.36
which I understand to mean that a program isn't registered. But which
program ?
James.
--
"Yield to temptation -- | Consultancy: james@cloud9.co.uk
it may not pass your way again" | http://www.cloud9.co.uk/james
|
- Lazarus Long | James Fidell
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/