From: Jason Lunz <lunz@falooley.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Blockbusting news, results get worse
Date: Mon, 27 Oct 2003 23:31:33 +0000 (UTC) [thread overview]
Message-ID: <slrnbpraml.2e6.lunz@absolut.localnet> (raw)
In-Reply-To: 3cba01c39c6f$141529a0$24ee4ca5@DIAMONDLX60
ndiamond@wta.att.ne.jp said:
> Yeah, I need to deliberately damage one block in order to test the
> firmware, but I don't want to damage multiple blocks and use up the
> reallocation space. I am a home user, even if I also do programming
> at work, even if I also volunteer one day each weekend to test Linux.
> How can I arrange to damage one block on a disk?
I have two ata100 drives sitting at home right now that fill dmesg with
lots of UnrecoverableErrors whenever you access certain sectors. I'll
ship them to anyone who will use them to make linux error recovery more
resilient, either at the ide driver level or in the filesystem.
any takers?
Jason
next prev parent reply other threads:[~2003-10-27 23:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 18:33 Blockbusting news, results get worse Mudama, Eric
2003-10-26 22:03 ` Andre Hedrick
2003-10-27 9:34 ` Norman Diamond
2003-10-27 10:23 ` Jan-Benedict Glaw
2003-10-27 23:31 ` Jason Lunz [this message]
2003-10-28 20:56 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2003-10-29 20:11 Mudama, Eric
2003-10-27 18:06 Mudama, Eric
2003-10-27 19:18 ` Andre Hedrick
2003-10-27 17:43 Mudama, Eric
2003-10-27 18:48 ` Hans Reiser
2003-10-27 19:47 ` Jeff Garzik
2003-10-27 20:03 ` John Bradford
2003-10-29 20:01 ` Pavel Machek
2003-10-30 8:30 ` John Bradford
2003-10-28 1:21 ` Pavel Machek
2003-10-28 12:54 ` Krzysztof Halasa
2003-10-27 13:07 Samium Gromoff
2003-10-26 22:12 Mudama, Eric
2003-10-26 7:37 Norman Diamond
2003-10-26 10:39 ` John Bradford
2003-10-26 9:41 ` Pavel Machek
2003-10-26 11:38 ` Norman Diamond
2003-10-26 11:56 ` Pavel Machek
2003-10-26 12:06 ` Hans Reiser
2003-10-26 13:59 ` Krzysztof Halasa
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=slrnbpraml.2e6.lunz@absolut.localnet \
--to=lunz@falooley.org \
--cc=linux-kernel@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