From: Rogier Wolff <R.E.Wolff@harddisk-recovery.nl>
To: Theodore Ts'o <tytso@mit.edu>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Driver retries disk errors.
Date: Tue, 31 Aug 2004 00:17:06 +0200 [thread overview]
Message-ID: <20040830221706.GA31968@bitwizard.nl> (raw)
In-Reply-To: <20040830174632.GA21419@thunk.org>
On Mon, Aug 30, 2004 at 01:46:32PM -0400, Theodore Ts'o wrote:
> > a filesystem: if we recover one block this way, the next block will be
> > errorred and the filesystem "crashes" anyway. In fact this behaviour
> > may masquerade the first warnings that something is going wrong....
>
> If the block gets successfully read after 2 or 3 tries, it might be a
> good idea for the kernel to automatically do a forced rewrite of the
> block, which should cause the disk to do its own disk block
> sparing/reassignment.
Hi Ted,
I agree that this is the theory. In practise however, I've never
seen it work correctly. We've seen several disks with say 1-5 bad
blocks and nothing else, and "dd if=/dev/zero of=/dev/<disk>" doesn't
seem to cure them.
Roger.
--
+-- Rogier Wolff -- www.harddisk-recovery.nl -- 0800 220 20 20 --
| Files foetsie, bestanden kwijt, alle data weg?!
| Blijf kalm en neem contact op met Harddisk-recovery.nl!
next prev parent reply other threads:[~2004-08-30 22:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 16:39 Driver retries disk errors Rogier Wolff
2004-08-30 17:46 ` Theodore Ts'o
2004-08-30 18:26 ` James Courtier-Dutton
2004-08-30 22:25 ` Rogier Wolff
2004-08-31 11:38 ` Alan Cox
2004-09-02 16:23 ` Eric Mudama
2004-08-31 15:16 ` Bill Davidsen
2004-08-30 22:17 ` Rogier Wolff [this message]
2004-08-31 11:45 ` Alan Cox
2004-08-31 13:45 ` Andre Hedrick
2004-08-31 13:54 ` Rogier Wolff
2004-08-31 14:12 ` Alan Cox
2004-08-31 15:56 ` Erik Mouw
2004-08-31 15:13 ` Alan Cox
2004-08-31 17:00 ` Erik Mouw
2004-08-31 16:12 ` Alan Cox
2004-09-01 15:18 ` Bill Davidsen
2004-09-01 14:46 ` Alan Cox
2004-09-01 18:54 ` Bill Davidsen
2004-09-01 15:28 ` Romano Giannetti
2004-09-01 14:44 ` Alan Cox
2004-09-01 23:14 ` Rogier Wolff
2004-09-02 9:29 ` Alan Cox
2004-09-02 10:54 ` Rogier Wolff
2004-09-02 14:30 ` John Stoffel
2004-09-02 14:59 ` Alan Cox
2004-09-02 16:07 ` John Stoffel
2004-09-02 16:26 ` Eric Mudama
2004-08-31 22:55 ` Christer Weinigel
[not found] <fa.d48te6f.1ol6tbb@ifi.uio.no>
[not found] ` <fa.eti1vu1.2nqlj5@ifi.uio.no>
2004-08-31 0:17 ` Robert Hancock
2004-09-01 23:04 ` Rogier Wolff
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=20040830221706.GA31968@bitwizard.nl \
--to=r.e.wolff@harddisk-recovery.nl \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.