From: Richard Smits <R.Smits@tudelft.nl>
To: linux-nfs@vger.kernel.org
Subject: Re: nfsv4 state id errors
Date: Thu, 06 Sep 2012 09:30:22 +0200 [thread overview]
Message-ID: <5048510E.4080407@tudelft.nl> (raw)
In-Reply-To: <503B49E4.2050409@tudelft.nl>
Anyone any ideas ? Or should we open a case at Netapp ?
Greetings.
On 08/27/2012 12:20 PM, Robbert Eggermont wrote:
> 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.
>
> (Client: SLED11 SP2, 3.0.34-0.7-default x86_64)
>
> The "hanging" seems to be caused by the server returning an
> NFS4ERR_BAD_STATEID(10025) status for PUTFH;LOCK and PUTFH;WRITE;GETATTR
> calls. The client is making several hundreds of these identical (same
> filehandle) calls each second.
>
> The problem seems to be triggered by (write) actions on an open file
> when the Kerberos ticket has expired (especially for .xsession-errors
> and files opened by Firefox or Thunderbird).
>
> When (after some time) a new valid ticket is obtained, the kernel
> reports this error:
> nfs4_reclaim_open_state: unhandled error -10026. Zeroing state
>
> Is this a client or a server problem (and is there by any chance a fix)?
>
> Robbert
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-09-06 7:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 10:20 nfsv4 state id errors Robbert Eggermont
2012-09-06 7:30 ` Richard Smits [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-17 15:57 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-17 15:54 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=5048510E.4080407@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).