linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Flynn <davidf@rd.bbc.co.uk>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: David Flynn <davidf@rd.bbc.co.uk>,
	"Myklebust, Trond" <Trond.Myklebust@netapp.com>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	linux-nfs@vger.kernel.org
Subject: Re: NFS4ERR_STALE_CLIENTID loop
Date: Mon, 31 Oct 2011 13:21:15 +0000	[thread overview]
Message-ID: <20111031132115.GJ2011@rd.bbc.co.uk> (raw)
In-Reply-To: <6FEDF9D0-B059-4580-931C-7EBBD1F8C8EA@oracle.com>

* Chuck Lever (chuck.lever@oracle.com) wrote:
> David, what would help immensely is if you can find a reliable way of
> reproducing this.  So far we have been unable to find a reproducer.

While i've managed to have problems with individual machines, that seem
to fail at some random point of their own choosing, the most reliable
way to produce problem for us to have a number of nodes updating various
RRD files frequently.

Given that i haven't found a reliable and short method for reproducing
it either, if we were to re-run the known case and capture all network
traffic, would you be able to extract the relevant detail to generate a
simulation?

Regards,

..david

  reply	other threads:[~2011-10-31 13:21 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
2011-10-29 21:12                                 ` Myklebust, Trond
2011-10-31 13:07                             ` Chuck Lever
2011-10-31 13:21                               ` David Flynn [this message]
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=20111031132115.GJ2011@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 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).