From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "John Bradford" <john@grabjohn.com>,
"Mudama, Eric" <eric_mudama@Maxtor.com>,
"'Hans Reiser '" <reiser@namesys.com>,
"'Wes Janzen '" <superchkn@sbcglobal.net>,
"'Rogier Wolff '" <R.E.Wolff@BitWizard.nl>,
<linux-kernel@vger.kernel.org>, <nikita@namesys.com>,
"'Pavel Machek '" <pavel@ucw.cz>,
"'Justin Cormack '" <justin@street-vision.com>,
"'Vitaly Fertman '" <vitaly@namesys.com>,
"'Krzysztof Halasa '" <khc@pm.waw.pl>
Subject: Re: Blockbusting news, results get worse
Date: Sun, 26 Oct 2003 20:38:53 +0900 [thread overview]
Message-ID: <358a01c39bb5$c651c7a0$24ee4ca5@DIAMONDLX60> (raw)
In-Reply-To: <200310261039.h9QAdniV000310@81-2-122-30.bradfords.org.uk>
John Bradford pretended to reply to me:
> > 4. When writing ZEROES to the bad sector, the drive reports SUCCESS.
> > But it lies. Subsequent attempts to read still fail. Subsequent
> > writing of zeroes appears to succeed again. Subsequent attempts to read
> > still fail.
>
> > I still have to say, we can't fix Toshiba, and we can avoid Toshiba, but
> > meanwhile we can fix Linux.
>
> How do you suggest we 'fix' 4, above, other than to flush the cache
> and verify each time a full sector of zeros is written to the disk?
Number 4 cannot be fixed by Linux. Why do you pervert my writing?
The refusal to remove a known defective block from ordinary use in the file
system can be fixed. How many times does this need to be said? Why do you
pretend that this is not what I have been saying in this entire thread?
If I understand Hans Reiser's message correctly, this fix has indeed been
made in ReiserFS version 4. I thank Mr. Reiser. (By the way, I volunteer
about one day each weekend for testing, and I am hardly in a position to
contribute funds. Please let's not beggar each other.)
By the way some participants in this thread have argued that the block
should not be replaced by zeroes or random garbage without notice. I fully
agree. The block should be replaced by zeroes or random garbage WITH
notice. From the point of view of logging it in the system log, it is
enough to log it once, it doesn't have to be logged over and over again.
>From the point of view of informing the user whose program is running, the
dd command does an excellent job, but some unknown program was remaining
silent when I/O errors were originally detected and logged. I still think
it is better to get that block out of the file system so that when that file
is rewritten or when other new files get created or extended then they won't
try to reuse that block. But I've said this enough too. I guess it's time
to stop beating this dead horse. But anyway Mr. Reiser understood, and I am
glad, and I thank him.
next prev parent reply other threads:[~2003-10-26 11:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2003-10-26 11:56 ` Pavel Machek
2003-10-26 12:06 ` Hans Reiser
2003-10-26 13:59 ` Krzysztof Halasa
2003-10-26 18:33 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
2003-10-28 20:56 ` Hans Reiser
2003-10-26 22:12 Mudama, Eric
2003-10-27 13:07 Samium Gromoff
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 18:06 Mudama, Eric
2003-10-27 19:18 ` Andre Hedrick
2003-10-29 20:11 Mudama, Eric
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='358a01c39bb5$c651c7a0$24ee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=R.E.Wolff@BitWizard.nl \
--cc=eric_mudama@Maxtor.com \
--cc=john@grabjohn.com \
--cc=justin@street-vision.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@namesys.com \
--cc=pavel@ucw.cz \
--cc=reiser@namesys.com \
--cc=superchkn@sbcglobal.net \
--cc=vitaly@namesys.com \
/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
Powered by JetHome