From: Michael Tokarev <mjt@tls.msk.ru>
To: andy liebman <andyliebman@aol.com>
Cc: david@dgreaves.com, linux-raid@vger.kernel.org
Subject: Re: Simulating Drive Failure on Mirrored OS drive
Date: Tue, 03 Oct 2006 00:20:31 +0400 [thread overview]
Message-ID: <4521748F.7000300@tls.msk.ru> (raw)
In-Reply-To: <45215240.1040301@aol.com>
andy liebman wrote:
>
>>
>> Read up on the md-faulty device.
>
> Got any links to this? As I said, we know how to set the device as
> faulty, but I'm not convinced this is a good simulation of a drive that
> fails (times out, becomes unresponsive, etc.)
Note that 'set device as faulty' is NOT the same as `md-faulty device'.
Read mdamd(8) manpage, and see options `-l' (level) and `-p' (parity)
for create mode.
/mjt
prev parent reply other threads:[~2006-10-02 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 23:55 Simulating Drive Failure on Mirrored OS drive andy liebman
2006-10-02 8:02 ` David Greaves
2006-10-02 17:54 ` andy liebman
2006-10-02 20:20 ` Michael Tokarev [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=4521748F.7000300@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=andyliebman@aol.com \
--cc=david@dgreaves.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 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).