linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "K.Tanaka" <k-tanaka@ce.jp.nec.com>
To: linux-scsi@vger.kernel.org
Cc: linux-raid@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [RFC] A SCSI fault injection framework using SystemTap.
Date: Tue, 22 Jan 2008 19:26:30 +0900	[thread overview]
Message-ID: <4795C4D6.9010904@ce.jp.nec.com> (raw)
In-Reply-To: <478C22A9.5000009@ce.jp.nec.com>


>The new framework is tested on Fedora8(i386) running with kernel 2.6.23.12.
>So far, I'm cleaning up the tool set for release, and plan to post it in the near future.

Now it's ready. The scsi fault injection tool is available from the following site.
https://sourceforge.net/projects/scsifaultinjtst/
If you have any comments, please let me know.

Additionally, the deadlock problem reproduced also on md RAID10. I think that the
same reason for RAID1 deadlock reported earlier cause this problem, because
raid10.c is based on raid1.c.
> e.g.
>  -The kernel thread for md RAID1 could cause a deadlock when the error handler for
>    md RAID1 contends with the write access to the md RAID1 array.

I've reproduced the deadlock on RAID10 using this tool with a small shell script for
automatically injecting a fault repeatedly. But I can't come up with any good
idea for the patch to fix this problem so far.

-- 
------------------------------------------------------------------------
Kenichi TANAKA    | Open Source Software Platform Development Division
                  | Computers Software Operations Unit, NEC Corporation
                  | k-tanaka@ce.jp.nec.com


      parent reply	other threads:[~2008-01-22 10:26 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
2008-01-15 11:17 ` Alasdair G Kergon
2008-01-22 10:26 ` K.Tanaka [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=4795C4D6.9010904@ce.jp.nec.com \
    --to=k-tanaka@ce.jp.nec.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-scsi@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).