From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: [RAID] forcing a read on a known bad block
Date: Wed, 12 Apr 2006 07:18:03 +0200 [thread overview]
Message-ID: <20060412051803.GA19309@percy.comedia.it> (raw)
In-Reply-To: <Pine.LNX.4.64.0604111232010.6603@taurus.cesta.com>
On Tue, Apr 11, 2006 at 12:37:53PM -1000, Julian Cowley wrote:
>On Tue, 11 Apr 2006, dean gaudet wrote:
>>anyhow this made me wonder if there's some other existing trick to force
>>such reads/reconstructions to occur... or perhaps this might be a useful
>>future feature.
>
>For testing RAID, what would be really nice is if there were a virtual
>disk device where one could simulate bad sectors (read or write),
>non-responsive disks, etc. It would be virtual in the same sort way
>that /dev/full simulates a full disk.
>
either use the MD "faulty" personality, or the device-mapper "error"
target.
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
prev parent reply other threads:[~2006-04-12 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 21:57 forcing a read on a known bad block dean gaudet
2006-04-11 22:15 ` Patrik Jonsson
2006-04-11 22:37 ` [RAID] " Julian Cowley
2006-04-12 5:18 ` Luca Berra [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=20060412051803.GA19309@percy.comedia.it \
--to=bluca@comedia.it \
--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).