From: Leon Woestenberg <leonw@mailcan.com>
To: linux-ide@vger.kernel.org
Subject: IDE layer adoptations that *fake* a failing drive?
Date: Fri, 14 May 2004 22:50:31 +0200 [thread overview]
Message-ID: <40A53117.1020305@mailcan.com> (raw)
Hello,
I wondered if anyone here is aware of code that sits between the IDE
software layer and the storage device, that emulates a failing disk in
one way or another.
I.e. for example, write multiple re-tries with time-outs, checksum
errors, failing to complete read/writes to medium etc.
From my networking stuff, I know there are network simulators that you
can provoke to simulate all kind of network traffic abnormalities, such
as congestion, dupes, lost packets, bursting.
I have access to only a limited number of really bad disks, and want to
do stress tests against fully automatically managed software RAID arrays
under Linux (except for the part where you have to physically swap
defect disks :-)
Ciao,
Leon.
next reply other threads:[~2004-05-14 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 20:50 Leon Woestenberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-14 23:17 IDE layer adoptations that *fake* a failing drive? Pat LaVarre
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=40A53117.1020305@mailcan.com \
--to=leonw@mailcan.com \
--cc=linux-ide@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).