From: Richard Smits <R.Smits@tudelft.nl>
To: linux-nfs@vger.kernel.org
Subject: nfsv4 state id errors
Date: Fri, 17 Aug 2012 17:54:50 +0200 [thread overview]
Message-ID: <502E694A.3020007@tudelft.nl> (raw)
Hello,
A couple of weeks agoo we upgraded our Netapp filer to 8.1.1RC1. We have
always had trouble with NFS and state id's. Resulting in hanging clients.
Some bugs were fixed in 8.1.1 but still trouble.
Now we have the following errors in our client messages file, after a hang.
What does this : NFS: "v4 server srv returned a bad sequence-id error!"
means ?
----
Aug 17 14:08:23 tudxxxxxx kernel: [622014.866818] NFS: v4 server srvxxx
returned a bad sequence-id error!
Aug 17 14:08:23 tudxxxxxx kernel: [622014.872143] NFS: v4 server
returned a bad sequence-id error on an unconfirmed sequence
ffff8801112dcc20!
Aug 17 14:08:23 tudxxxxxx kernel: [622014.872871] NFS: v4 server
returned a bad sequence-id error on an unconfirmed sequence
ffff8801112dcc20!
Aug 17 14:08:23 tudxxxxxx kernel: [622015.170658] NFS: v4 server
returned a bad sequence-id error on an unconfirmed sequence
ffff8801112e6820!
Aug 17 14:08:23 tudxxxxxx kernel: [622015.278260] NFS: v4 server srvxxx
returned a bad sequence-id error!
Aug 17 14:08:23 tudxxxxxx kernel: [622015.651868] NFS: v4 server srvxxx
returned a bad sequence-id error!
Aug 17 14:08:24 tudxxxxxx kernel: [622016.051741] NFS: v4 server srvxxx
returned a bad sequence-id error!
Aug 17 14:08:25 tudxxxxxx kernel: [622017.155713] NFS: v4 server srvxxx
returned a bad sequence-id error!
Aug 17 14:08:25 tudxxxxxx kernel: [622017.346225] NFS: v4 server
returned a bad sequence-id error on an unconfirmed sequence
ffff8800bcf39620!
Aug 17 14:08:25 tudxxxxxx kernel: [622017.349781] NFS: v4 server
returned a bad sequence-id error on an unconfirmed sequence
ffff8800bcf39620!
Aug 17 14:08:25 tudxxxxxx kernel: [622017.350840] NFS: v4 server
returned a bad sequence-id error on an unconfirmed sequence
ffff8800bcf39620!
next reply other threads:[~2012-08-17 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 15:54 Richard Smits [this message]
2012-08-17 15:57 nfsv4 state id errors Richard
2012-08-17 18:18 ` Myklebust, Trond
2012-08-17 18:34 ` Richard
2012-08-17 18:40 ` Myklebust, Trond
2012-08-17 18:44 ` Richard Smits
2012-08-27 10:20 Robbert Eggermont
2012-09-06 7:30 ` Richard Smits
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=502E694A.3020007@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.