Hello,
We have a open support case at Netapp for this but I hope someone
recognizes these errors and can give us a clue how to solve this.
We have a Netapp 3170 NFS4 server with krb5 security. Our Suse 11.2
clients give these errors.
---------------------------------------
RPC call returned error 13
NFS: v4 server returned a bad sequence-id error on an unconfirmed
sequence ffff88020d80de20!
nfs4_reclaim_locks: unhandled error -10026. Zeroing state
nfs4_reclaim_open_state: unhandled error -10026. Zeroing state
NFS: v4 server srvxxx returned a bad sequence-id error!
---------------------------------------
After the last line (zeroing state) the client goes into a hang.
Client versions :
nfs-client-1.2.3-18.23.1
krb5-client-1.6.3-133.48.48.1
Kernel : 3.0.38-0.5-default
I have reported this earlier on this list, but i hope someone reads it
who recognises it. Will save us a lot of headaches....
Greetings, Richard Smits
ICT, Technical University Delft.
The Netherlands
R.Smits@xxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
