From: "K.Tanaka" <k-tanaka@ce.jp.nec.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [RFC] A SCSI fault injection framework using SystemTap.
Date: Tue, 15 Jan 2008 18:54:06 +0900 [thread overview]
Message-ID: <478C82BE.6040100@ce.jp.nec.com> (raw)
In-Reply-To: <20080115033145.GR18741@parisc-linux.org>
Matthew Wilcox wrote:
> On Tue, Jan 15, 2008 at 12:04:09PM +0900, K.Tanaka wrote:
>> I would like to introduce a SCSI fault injection framework using SystemTap.
>>
>> Currently, kernel has Fault-injection framework and Faulty mode for md,
>> which can also be used for testing the error handling. But, they could
>> only produce fixed type of errors stochastically. In order to simulate
>> more realistic scsi disk faults, I have created a new flexible fault injection
>> framework using SystemTap.
>
> How does it compare to using scsi_debug, which I believe can do all of
> the above and more?
>
Sorry for the lack of explanation.
The new framework is supposed to be used by a userspace testing tool
(such as a shell script). For the availability, this framework enables user to
designate the inode number of the target file on the device to inject faults.
On accessing the target file through page caches, a fault will be injected.
Also, user can designate the logical block address as the target position
of a fault injection.
--
---------------------------------------------------------
Kenichi TANAKA | Open Source Software Platform Development Division
| Computers Software Operations Unit, NEC Corporation
| k-tanaka@ce.jp.nec.com
next prev parent reply other threads:[~2008-01-15 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 3:04 [RFC] A SCSI fault injection framework using SystemTap K.Tanaka
2008-01-15 3:31 ` Matthew Wilcox
2008-01-15 9:54 ` K.Tanaka [this message]
2008-01-15 11:17 ` Alasdair G Kergon
2008-01-22 10:26 ` K.Tanaka
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=478C82BE.6040100@ce.jp.nec.com \
--to=k-tanaka@ce.jp.nec.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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).