From: David Flynn <davidf@rd.bbc.co.uk>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: David Flynn <davidf@rd.bbc.co.uk>,
Chuck Lever <chuck.lever@oracle.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org
Subject: Re: NFS4ERR_STALE_CLIENTID loop
Date: Sat, 29 Oct 2011 21:07:41 +0000 [thread overview]
Message-ID: <20111029210741.GF2011@rd.bbc.co.uk> (raw)
In-Reply-To: <2E1EB2CF9ED1CB4AA966F0EB76EAB4430BDE7481@SACMVEXC2-PRD.hq.netapp.com>
* Myklebust, Trond (Trond.Myklebust@netapp.com) wrote:
> BAD_STATEID is a different matter, and is one that we should have
> resolved in the NFS client in the upstream kernel. At least on newer
> clients, we should be trying to reopen the file and re-establish all
> locks when we get a BAD_STATEID. Can you please remind us which kernel
> you are using?
Ah, i see. This was all on 3.0.0 and 3.0.4 (a quick check didn't reveal
any relevant changes between the two).
Are there any stable patches that can be applied to 3.0.y?
> That said... Even on new clients, the recovery attempt may fail due to
> the STALE_CLIENTID bug. That will still hit us when we call OPEN in
> order to get a new stateid.
The interval between retries on that was ~1-1.5ms, could this be made
slower? -- same questions as before really.
Regards,
..david
next prev parent reply other threads:[~2011-10-29 21:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 10:40 NFS4 BAD_STATEID loop (kernel 3.0) David Flynn
2011-10-24 11:22 ` Trond Myklebust
2011-10-24 13:17 ` David Flynn
2011-10-24 13:32 ` Trond Myklebust
2011-10-24 14:50 ` NFS4 BAD_STATEID loop (kernel 3.0.4) David Flynn
2011-10-24 15:31 ` Trond Myklebust
2011-10-24 15:55 ` David Flynn
2011-10-27 22:17 ` David Flynn
2011-10-29 0:25 ` NFS4ERR_STALE_CLIENTID loop David Flynn
2011-10-29 17:29 ` Trond Myklebust
2011-10-29 18:02 ` David Flynn
2011-10-29 18:22 ` Myklebust, Trond
2011-10-29 18:23 ` Chuck Lever
2011-10-29 18:26 ` Myklebust, Trond
2011-10-29 18:29 ` David Flynn
2011-10-29 18:15 ` J. Bruce Fields
2011-10-29 18:21 ` Myklebust, Trond
2011-10-29 18:47 ` J. Bruce Fields
2011-10-29 18:50 ` Chuck Lever
2011-10-29 19:19 ` Myklebust, Trond
2011-10-29 19:52 ` David Flynn
2011-10-29 20:42 ` Myklebust, Trond
2011-10-29 21:07 ` David Flynn [this message]
2011-10-29 21:12 ` Myklebust, Trond
2011-10-31 13:07 ` Chuck Lever
2011-10-31 13:21 ` David Flynn
2011-10-31 13:39 ` Chuck Lever
2011-10-24 13:43 ` NFS4 BAD_STATEID loop (kernel 3.0) Chuck Lever
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=20111029210741.GF2011@rd.bbc.co.uk \
--to=davidf@rd.bbc.co.uk \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--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.