From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Driver retries disk errors.
Date: Mon, 30 Aug 2004 18:17:24 -0600 [thread overview]
Message-ID: <002e01c48eef$e3e2dc40$6601a8c0@northbrook> (raw)
In-Reply-To: fa.eti1vu1.2nqlj5@ifi.uio.no
Quite likely, in that case the drive has exhausted its spare pool, and there
are a bunch of bad sectors that have already been reallocated. Some drives
will reallocate sectors if they are still readable but the sector appears to
be marginal.
----- Original Message -----
From: "Rogier Wolff" <R.E.Wolff@harddisk-recovery.nl>
Newsgroups: fa.linux.kernel
To: "Theodore Ts'o" <tytso@mit.edu>; <linux-kernel@vger.kernel.org>;
<linux-ide@vger.kernel.org>
Sent: Monday, August 30, 2004 4:19 PM
Subject: Re: Driver retries disk errors.
> 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!
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2004-08-31 3:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.d48te6f.1ol6tbb@ifi.uio.no>
[not found] ` <fa.eti1vu1.2nqlj5@ifi.uio.no>
2004-08-31 0:17 ` Robert Hancock [this message]
2004-09-01 23:04 ` Driver retries disk errors Rogier Wolff
2004-08-30 16:39 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
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
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='002e01c48eef$e3e2dc40$6601a8c0@northbrook' \
--to=hancockr@shaw.ca \
--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