From: Richard Smits <R.Smits@tudelft.nl>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: nfs4 state id errors
Date: Wed, 24 Oct 2012 15:04:56 +0200 [thread overview]
Message-ID: <5087E778.4040909@tudelft.nl> (raw)
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@tudelft.nl
reply other threads:[~2012-10-24 13:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5087E778.4040909@tudelft.nl \
--to=r.smits@tudelft.nl \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).