All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: kedacomkernel <kedacomkernel@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Add set bad lba function in md-faulty module.
Date: Tue, 15 May 2012 10:16:11 +1000	[thread overview]
Message-ID: <20120515101611.4f2aaba0@notabene.brown> (raw)
In-Reply-To: <201205141822219532629@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]

On Mon, 14 May 2012 18:22:25 +0800 "kedacomkernel" <kedacomkernel@gmail.com>
wrote:

> Hi all:
> 	In order to test md code, sometime we need  simulate read/write harddisk error.
> 	Using hdparm --make-bad-sector to  simulate  read error.But I did not find way of  simulating write-error.
> 	I tested md-faulty module, it can do this.But it is not provide the function link hdparm --make-bad-sector,which did not set lba.
> 	Using hdpamr --make-bad-sector to  simulate read error can cause some problem.
> 	It will cause ata commnd reset,disk reset and so on.It take too log time.
> 	So I think add a function in md-faulty which can set read/write lba.
> 	How about ?

I don't know how --make-bad-sector works so it might not be possible to get
md to respond to the same command.  But if it can work it sounds like a good
idea.

Patches welcome.

NeilBrown


>  				
> --------------
> kedacomkernel
> 2012-05-14
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-05-15  0:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 10:22 Add set bad lba function in md-faulty module kedacomkernel
2012-05-15  0:16 ` NeilBrown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-05-15 11:49 majianpeng
2012-05-17 11:49 ` George Shuklin

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=20120515101611.4f2aaba0@notabene.brown \
    --to=neilb@suse.de \
    --cc=kedacomkernel@gmail.com \
    --cc=linux-raid@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.