From: Krzysztof Halasa <khc@pm.waw.pl>
To: John Bradford <john@grabjohn.com>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>,
Norman Diamond <ndiamond@wta.att.ne.jp>,
Hans Reiser <reiser@namesys.com>,
Wes Janzen <superchkn@sbcglobal.net>,
linux-kernel@vger.kernel.org
Subject: Re: Blockbusting news, this is important (Re: Why are bad disk sectors numbered strangely, and what happens to them?)
Date: 17 Oct 2003 13:24:10 +0200 [thread overview]
Message-ID: <m3zng0yun9.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <200310171049.h9HAnBbO000594@81-2-122-30.bradfords.org.uk>
John Bradford <john@grabjohn.com> writes:
> Besides, are you positive that you always got the correct data off the
> disk? See the discussions about hashing algorithms - maybe the drive
> simply returned data that had an additional bit flipped and wasn't
> identified as bad.
One bit? No chance. The same as with ECC RAM - one bit error will always
be detected.
> If you are having to try over 1000 times from
> userspace, the drive is in a bad way. You shouldn't really make
> assumptions that you do usually, (that the error correction is good
> enough to ensure bad data isn't returned as good data). If you are
> recovering data from a spreadsheet, for example, the errors could go
> unnoticed, but have catastrophic results.
Then you have to abandon using any hard drivers. Or computers at all.
Well, mirrors (with read-and-compare) are probably good enough for you,
but it has to be done at application level.
> Of course you will - it's remapped, the data isn't overwritten! You
> may need more advanced tools,
= in practice, it's lost. Have you seen such tools?
> but you can still seek the heads to that
> part of the platter and get data from the head-amp. Just because you
> couldn't use your simple method anymore is real reason to argue
> against fixing the problem.
against _changing_ the problem (it doesn't go away), breaking things
which are now sane.
> This may be more sensible, but not for the reasons you are suggesting,
> and not in the way that you are suggesting.
Then note that a drive can be temporarily unable to read most of the
data - due to, say, incorrect supply voltage or very high level of
electromagnetic interferences.
Would you like to trash _all_ your data in such case automatically?
> Suspect drive? Bin it. Do you really not value your data enough to
> do that?
Do you really not value your data enough to mark it as inaccessible?
If it comes to non-standard recovery then you should rather go for
backups.
--
Krzysztof Halasa, B*FH
next prev parent reply other threads:[~2003-10-17 19:03 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 9:31 Why are bad disk sectors numbered strangely, and what happens to them? Norman Diamond
[not found] ` <200310131014.h9DAEwY3000241@81-2-122-30.bradfords.org.uk>
2003-10-13 10:24 ` Norman Diamond
2003-10-13 10:33 ` John Bradford
2003-10-13 11:30 ` Norman Diamond
2003-10-13 11:58 ` Maciej Zenczykowski
2003-10-15 10:22 ` Norman Diamond
2003-10-13 12:02 ` John Bradford
2003-10-15 10:23 ` Norman Diamond
2003-10-15 18:56 ` Pavel Machek
2003-10-14 6:54 ` Rogier Wolff
2003-10-13 14:24 ` Chuck Campbell
2003-10-13 14:54 ` Maciej Zenczykowski
2003-10-13 16:29 ` Roger Larsson
2003-10-14 6:49 ` Rogier Wolff
2003-10-14 7:05 ` Wes Janzen
2003-10-14 7:21 ` John Bradford
2003-10-14 7:40 ` Rogier Wolff
2003-10-14 8:11 ` John Bradford
2003-10-14 8:45 ` Hans Reiser
2003-10-14 9:46 ` Rogier Wolff
2003-10-14 9:57 ` Hans Reiser
2003-10-14 10:10 ` Rogier Wolff
2003-10-14 10:31 ` Hans Reiser
2003-10-14 10:19 ` John Bradford
[not found] ` <200310140800.h9E80BT9000815@81-2-122-30.bradfords.org.uk>
[not found] ` <20031014081110.GA14418@bitwizard.nl>
2003-10-14 8:55 ` Wes Janzen
2003-10-14 10:05 ` Rogier Wolff
2003-10-14 7:24 ` Rogier Wolff
2003-10-14 9:04 ` Hans Reiser
2003-10-15 10:23 ` Norman Diamond
2003-10-15 10:39 ` Hans Reiser
2003-10-17 9:40 ` Blockbusting news, this is important (Re: Why are bad disk sectors numbered strangely, and what happens to them?) Norman Diamond
2003-10-17 9:48 ` Hans Reiser
2003-10-17 11:11 ` Norman Diamond
2003-10-17 11:45 ` Hans Reiser
2003-10-17 11:51 ` John Bradford
2003-10-17 12:53 ` John Bradford
2003-10-17 13:03 ` Russell King
2003-10-17 13:26 ` John Bradford
2003-10-19 7:50 ` Andre Hedrick
2003-10-17 13:04 ` Russell King
2003-10-17 14:09 ` Norman Diamond
2003-10-17 9:58 ` Pavel Machek
2003-10-17 10:15 ` Hans Reiser
2003-10-17 10:24 ` Rogier Wolff
2003-10-17 10:49 ` John Bradford
2003-10-17 11:09 ` Rogier Wolff
2003-10-17 11:24 ` Krzysztof Halasa [this message]
2003-10-17 19:35 ` John Bradford
2003-10-17 23:28 ` Krzysztof Halasa
2003-10-18 7:42 ` Pavel Machek
2003-10-18 8:30 ` John Bradford
2003-10-21 20:26 ` bill davidsen
2003-10-18 8:27 ` John Bradford
2003-10-18 12:02 ` Krzysztof Halasa
2003-10-18 16:26 ` Nuno Silva
2003-10-18 20:16 ` Krzysztof Halasa
[not found] ` <m37k33igui.fsf@defiant. <m3u166vjn0.fsf@defiant.pm.waw.pl>
2003-10-21 20:39 ` bill davidsen
2003-10-17 10:37 ` ATA Defect management John Bradford
2003-10-21 20:44 ` bill davidsen
2003-10-17 12:08 ` Blockbusting news, this is important (Re: Why are bad disk sectors numbered strangely, and what happens to them?) Justin Cormack
2003-10-21 20:12 ` bill davidsen
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=m3zng0yun9.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=R.E.Wolff@BitWizard.nl \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.jp \
--cc=reiser@namesys.com \
--cc=superchkn@sbcglobal.net \
/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
all inboxes | Powered by JetHome®