All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Andi Kleen <ak@suse.de>
Cc: Andreas Dilger <adilger@turbolinux.com>,
	monkeyiq <monkeyiq@users.sourceforge.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Dying disk and filesystem choice.
Date: Thu, 24 May 2001 12:19:36 +0200	[thread overview]
Message-ID: <20010524121936.I12470@suse.de> (raw)
In-Reply-To: <m3bsoj2zsw.fsf@kloof.cr.au> <200105240658.f4O6wEWq031945@webber.adilger.int> <20010524103145.A9521@gruyere.muc.suse.de>
In-Reply-To: <20010524103145.A9521@gruyere.muc.suse.de>; from ak@suse.de on Thu, May 24, 2001 at 10:31:45AM +0200

On Thu, May 24 2001, Andi Kleen wrote:
> On Thu, May 24, 2001 at 12:58:14AM -0600, Andreas Dilger wrote:
> > Well reiserfs is probably a very bad choice at this point.  It
> > does not have any bad blocks support (yet), so as soon as you have
> > a bad block you are stuck.
> 
> reiserfs doesn't, but the HD usually has transparently in its firmware.
> So it hits a bad block; you see an IO error and the next time you hit
> the block the firmware has mapped in a fresh one from its internal
> reserves.

In fact you will typically only see an I/O error if the drive _can't_
remap the sector anymore, because it has run out. No point in reporting
a condition that was recovered.

I'd still say, that if you get bad block errors reported from your disk
it's long overdue for replacement.

-- 
Jens Axboe


  reply	other threads:[~2001-05-24 10:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-24  3:25 Dying disk and filesystem choice monkeyiq
2001-05-24  6:03 ` Hans Reiser
2001-05-24  6:58 ` Andreas Dilger
2001-05-24  8:31   ` Andi Kleen
2001-05-24 10:19     ` Jens Axboe [this message]
2001-05-24 12:08       ` monkeyiq
2001-05-24 15:46       ` Jonathan Lundell
2001-05-24 15:50     ` Jonathan Lundell
2001-05-24 15:56       ` Andi Kleen
2001-05-24 16:13         ` Jonathan Lundell
2001-05-24 16:53     ` Hans Reiser
2001-05-24 17:16       ` David Rees
2001-05-24 19:03       ` J Sloan
2001-05-24 20:54         ` Hans Reiser
2001-05-24 19:46       ` Erik Mouw
2001-05-24 21:24         ` Hans Reiser
2001-05-24 22:16         ` Alan Cox
2001-05-25 13:21           ` Chris Mason
2001-05-25 16:21             ` Hans Reiser
2001-05-25 16:58               ` Chris Mason
2001-05-25 17:42                 ` Hans Reiser
2001-05-25 11:29         ` Juan Quintela
2001-05-24 21:35       ` monkeyiq
  -- strict thread matches above, loose matches on Subject: below --
2001-05-24 17:30 Cress, Andrew R

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=20010524121936.I12470@suse.de \
    --to=axboe@suse.de \
    --cc=adilger@turbolinux.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monkeyiq@users.sourceforge.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 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.