From: Jens Axboe <axboe@suse.de>
To: Kevin Corry <kevcorry@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, Lars Marowsky-Bree <lmb@suse.de>,
braam <braam@clusterfs.com>,
torvalds@osdl.org, akpm@osdl.org,
"'Phil Schwan'" <phil@clusterfs.com>
Subject: Re: [PATCH/RFC] Lustre VFS patch
Date: Tue, 25 May 2004 15:55:36 +0200 [thread overview]
Message-ID: <20040525135535.GT1952@suse.de> (raw)
In-Reply-To: <200405250835.24110.kevcorry@us.ibm.com>
On Tue, May 25 2004, Kevin Corry wrote:
> On Tuesday 25 May 2004 5:52 am, Lars Marowsky-Bree wrote:
> > Maybe you could fix this in the test harness / Lustre itself instead and
> > silently discard the writes internally if told so via an (internal)
> > option, instead of needing a change deeper down in the IO layer, or use
> > a DM target which can give you all the failure scenarios you need?
> >
> > In particular the last one - a fault-injection DM target - seems like a
> > very valuable tool for testing in general, but the Lustre-internal
> > approach may be easier in the long run.
>
> See dm-flakey.c in the latest -udm patchset for a fairly simple version of a
> "fault-injection" target.
>
> http://sources.redhat.com/dm/patches.html
Would by far be the superior solution.
--
Jens Axboe
next prev parent reply other threads:[~2004-05-25 13:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 11:39 [PATCH/RFC] Lustre VFS patch Peter J. Braam
2004-05-24 11:46 ` Jens Axboe
2004-05-25 1:48 ` braam
2004-05-25 6:47 ` Jens Axboe
2004-05-25 8:21 ` braam
2004-05-25 8:27 ` Jens Axboe
2004-05-25 10:52 ` Lars Marowsky-Bree
2004-05-25 11:45 ` braam
2004-05-25 13:35 ` Kevin Corry
2004-05-25 13:55 ` Jens Axboe [this message]
2004-05-24 12:00 ` hch
2004-05-24 12:01 ` hch
2004-05-24 12:03 ` hch
2004-05-24 15:33 ` Horst von Brand
2004-05-25 20:43 ` hch
2004-05-24 12:05 ` hch
2004-05-24 18:06 ` Trond Myklebust
2004-05-25 8:21 ` braam
2004-05-24 12:08 ` hch
2004-05-24 13:44 ` Arjan van de Ven
2004-05-24 13:53 ` viro
2004-05-28 16:56 ` braam
2004-05-28 17:00 ` Christoph Hellwig
2004-05-24 14:19 ` viro
2004-05-28 23:18 ` Maneesh Soni
2004-05-29 17:53 ` Anton Blanchard
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=20040525135535.GT1952@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=braam@clusterfs.com \
--cc=kevcorry@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
--cc=phil@clusterfs.com \
--cc=torvalds@osdl.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