From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Norman Diamond" <ndiamond@wta.att.ne.jp>
Cc: "Mudama, Eric" <eric_mudama@Maxtor.com>,
"'Hans Reiser '" <reiser@namesys.com>,
"'Wes Janzen '" <superchkn@sbcglobal.net>,
"'Rogier Wolff '" <R.E.Wolff@BitWizard.nl>,
"'John Bradford '" <john@grabjohn.com>,
<linux-kernel@vger.kernel.org>, <nikita@namesys.com>,
"'Pavel Machek '" <pavel@ucw.cz>,
"'Justin Cormack '" <justin@street-vision.com>,
"'Vitaly Fertman '" <vitaly@namesys.com>
Subject: Re: Blockbusting news, results end
Date: 27 Oct 2003 11:48:57 +0100 [thread overview]
Message-ID: <m3u15vdkh2.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <3cbb01c39c6f$17608410$24ee4ca5@DIAMONDLX60>
"Norman Diamond" <ndiamond@wta.att.ne.jp> writes:
> Bingo. This is why reallocation at the time of a failed read is also
> necessary. Yes the data are lost, yes the failure needs to be both logged
> (once)
The log entry may be easily lost. Especially when the drive is failing.
> and displayed to the user (once),
To which user??? Hard drive sectors have no users.
> yes if an application reads it
> again before writing then it will be garbage or zeroes,
I hope drive makers won't take it seriously.
> but get the LBA
> sector number moved to a place that is less likely to be unreliable.
So you rather want to read garbage than get a real I/O error.
The only situation I can imagine which benefits from such an approach
is playing an audio-video stream.
> Meanwhile software must still make up for defective firmware.
Yeah. yeah. Only "if (drive_is_toshiba()) BUG()" comes to my mind.
--
Krzysztof Halasa, B*FH
next prev parent reply other threads:[~2003-10-27 17:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 18:39 Blockbusting news, results end Mudama, Eric
2003-10-27 9:45 ` Norman Diamond
2003-10-27 10:48 ` Krzysztof Halasa [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-28 16:10 Mudama, Eric
2003-10-28 18:30 ` bill davidsen
2003-10-28 11:31 Norman Diamond
2003-10-27 17:50 Mudama, Eric
2003-10-26 8:49 Norman Diamond
2003-10-26 9:22 ` Pavel Machek
2003-10-26 11:25 ` Norman Diamond
2003-10-27 20:58 ` jw schultz
2003-10-27 22:27 ` Andre Hedrick
2003-10-27 22:57 ` jw schultz
2003-10-28 2:03 ` jw schultz
2003-10-26 11:01 ` Hans Reiser
2003-10-26 12:59 ` Oleg Drokin
2003-10-26 12:05 ` Hans Reiser
2003-10-26 12:39 ` Oleg Drokin
2003-10-26 16:26 ` Hans Reiser
2003-10-26 17:13 ` Oleg Drokin
2003-10-26 18:20 ` Hans Reiser
2003-10-26 19:07 ` Oleg Drokin
2003-10-27 12:44 ` Vitaly Fertman
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=m3u15vdkh2.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=R.E.Wolff@BitWizard.nl \
--cc=eric_mudama@Maxtor.com \
--cc=john@grabjohn.com \
--cc=justin@street-vision.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.jp \
--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;
as well as URLs for NNTP newsgroup(s).