From: "J. Bruce Fields" <bfields@fieldses.org>
To: Bryan Schumaker <bjschuma@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v3 1/3] NFSD: Added fault injection
Date: Fri, 30 Sep 2011 11:05:58 -0400 [thread overview]
Message-ID: <20110930150558.GE19125@fieldses.org> (raw)
In-Reply-To: <4E85D81F.3080108@netapp.com>
On Fri, Sep 30, 2011 at 10:54:23AM -0400, Bryan Schumaker wrote:
> On 09/30/2011 10:35 AM, J. Bruce Fields wrote:
> > On Thu, Sep 29, 2011 at 02:59:23PM -0400, bjschuma@netapp.com wrote:
> >> From: Bryan Schumaker <bjschuma@netapp.com>
> >>
> >> Fault injection on the NFS server makes it easier to test the client's
> >> state manager and recovery threads. Simulating errors on the server is
> >> easier than finding the right conditions that cause them naturally.
> >
> > You also might look at the unlock_ip interface that Wendy Cheng added a
> > few years ago. The fact that it doesn't remove nfsv4 state is really a
> > bug, it should be blowing away any relevant v4 clients as the same time.
> >
> > (Though note the IP in question is a server IP, not a client IP.)
>
> I'll take a look. Thanks for the warning that it looks for a server IP, but would passing the client IP be more useful?
It was designed for people using floating IP's to make their server look
like multiple servers, who want to shut down just the client's using one
of the floating IP's.
> > Is this the forget_n_clients scenario really a useful one to test?
> > I'd've thought that the client would need to deal with the entire client
> > diseappearing (due to network partition, for example), but not normally
> > individual open owners.
>
> It might not be a normal case, but it still could be interesting to see how the client recovers.
>
> I was mostly looking at what state the server tracks and deleting what I could find.
I think it would be more interesting to find out what typical failure
scenarios are and then figure out how to simulate them.
--b.
prev parent reply other threads:[~2011-09-30 15:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 18:59 [PATCH v3 1/3] NFSD: Added fault injection bjschuma
2011-09-29 18:59 ` [PATCH v3 2/3] NFSD: Added fault injection script bjschuma
2011-09-29 18:59 ` [PATCH v3 3/3] NFSD: Added fault injection documentation bjschuma
2011-09-29 19:06 ` [PATCH v3 1/3] NFSD: Added fault injection Chuck Lever
2011-09-29 19:15 ` Bryan Schumaker
2011-09-29 19:22 ` Chuck Lever
2011-09-29 19:26 ` Bryan Schumaker
2011-09-29 20:14 ` Bryan Schumaker
2011-09-30 14:28 ` Chuck Lever
2011-09-30 14:30 ` J. Bruce Fields
2011-09-30 14:38 ` Bryan Schumaker
2011-09-30 14:57 ` Chuck Lever
2011-09-30 15:05 ` Bryan Schumaker
2011-09-30 14:35 ` J. Bruce Fields
2011-09-30 14:54 ` Bryan Schumaker
2011-09-30 15:05 ` J. Bruce Fields [this message]
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=20110930150558.GE19125@fieldses.org \
--to=bfields@fieldses.org \
--cc=bjschuma@netapp.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).