All of lore.kernel.org
 help / color / mirror / Atom feed
From: majianpeng <majianpeng@gmail.com>
To: "George Shuklin" <george.shuklin@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Re: Add set bad lba function in md-faulty module.
Date: Fri, 18 May 2012 16:41:04 +0800	[thread overview]
Message-ID: <201205181641012658677@gmail.com> (raw)
In-Reply-To: 201205151949130004425@gmail.com

Thanks. In fact, using md-faulty also do that,but must do more steps. So I think add it in md-faulty.

------------------				 
majianpeng
2012-05-18

-------------------------------------------------------------
发件人:George Shuklin
发送日期:2012-05-17 19:49:26
收件人:majianpeng
抄送:linux-raid
主题:Re: Add set bad lba function in md-faulty module.



On 15.05.2012 15:49, majianpeng 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 ?
> 											
>   				
How about using an iscsi at localhost? Export disk via ISCSI target, 
connect to it with initiator. With iptables and open-iscsi settings you 
can precisely control error behavior and imitate all kinds of errors 
(including timeouts).

      parent reply	other threads:[~2012-05-18  8:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 11:49 Add set bad lba function in md-faulty module majianpeng
2012-05-17 11:49 ` George Shuklin
2012-05-18  8:41 ` majianpeng [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=201205181641012658677@gmail.com \
    --to=majianpeng@gmail.com \
    --cc=george.shuklin@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.