linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Rogier Wolff <R.E.Wolff@harddisk-recovery.nl>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Driver retries disk errors.
Date: Mon, 30 Aug 2004 13:46:32 -0400	[thread overview]
Message-ID: <20040830174632.GA21419@thunk.org> (raw)
In-Reply-To: <20040830163931.GA4295@bitwizard.nl>

On Mon, Aug 30, 2004 at 06:39:31PM +0200, Rogier Wolff wrote:
> We encounter "bad" drives with quite a lot more regularity than other
> people (look at the Email address). We're however, wondering why the
> IDE code still retries a bad block 8 times? 

I could see retrying 2 or 3 times, but 8 times does seem to be a bit
much, agreed.

> In fact we regularly are able to recover data from drives: we have a
> userspace application that retries over and over again, and this
> sometimes recovers "marginal" blocks. This could be considered "good
> practise" if there is a filesystem requesting the block. On the other
> hand, when this happens, the drive is usually beyond being usable for
> 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.  

						- Ted

  reply	other threads:[~2004-08-30 17:47 UTC|newest]

Thread overview: 16+ 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 [this message]
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-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-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=20040830174632.GA21419@thunk.org \
    --to=tytso@mit.edu \
    --cc=R.E.Wolff@harddisk-recovery.nl \
    --cc=linux-ide@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).