Hi all,
We've just changed some of our servers over to NFSv4, and we have
noticed that if a program on a NFS client opens a file read-only and
then tries to obtain an exclusive lock on that file, the server logs the
following to the kernel log:
NFSD: preprocess_seqid_op: bad seqid (expected 4, got 5)
And the NFS client logs this corresponding entry to its logs:
NFS: v4 server 10.16.101.2 returned a bad sequence-id error!
Is this the desired behaviour? Or should the NFS server allow the
exclusive lock to be acquired by a process that has opened a file
read-only? (or has this been fixed in a newer release of the nfs server
code?) The NFS server is using the standard Debian kernel for Etch
(2.6.18-5-amd64).
The NFS clients are running a variety of kernels as follows:
2.6.22-2-amd64 (from http://www.backports.org)
2.6.23-1-amd64 (from
http://kernel-archive.buildserver.net/debian-kernel/pool/main/l/linux-2.
6/)
2.6.18-5-686 (current kernel from Etch)
Steven
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued.
Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs