mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Cress, Andrew R" <andrew.r.cress@intel.com>
To: "'Jonathan Lundell'" <jlundell@pobox.com>,
	Jens Axboe <axboe@suse.de>, 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 10:30:43 -0700	[thread overview]
Message-ID: <9678C2B4D848D41187450090276D1FAE0635F05A@FMSMSX32> (raw)

>At 12:19 PM +0200 2001-05-24, Jens Axboe wrote:
>>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.

On Thursday, May 24, 2001 11:46 AM, Jonathan Lundell wrote:
>This can't be right. It implies that the drive is returning bogus 
>data with no error indication. Remapping a bad sector is not the same 
>as recovering it.

The automatic reallocation of bad spots on a drive is safe unless paired
with the write cache enabled bit in the disk mode pages (configuration).
WCE, in some cases, can cause the write/read to both take place from cache
with good status, and if the bad spot is reallocated later, when the cache
is flushed, the reporting gets very confusing.

In general:
It is a common misconception that if a disk begins to show some bad spots,
that it should be replaced.  In fact, a disk can have a reliable, useful
life for years after bad spots begin to show up.  The number of bad spots in
the Grown Defect List over a specified time as a % of capacity can be an
predictor of impending failure, however.

Andy Cress



             reply	other threads:[~2001-05-24 17:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-24 17:30 Cress, Andrew R [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-24  3:25 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
2001-05-24 12:08       ` monkeyiq
2001-05-24 15:46     ` 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
2001-05-24 15:50   ` Jonathan Lundell
2001-05-24 15:56     ` Andi Kleen
2001-05-24 16:13     ` Jonathan Lundell

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=9678C2B4D848D41187450090276D1FAE0635F05A@FMSMSX32 \
    --to=andrew.r.cress@intel.com \
    --cc=adilger@turbolinux.com \
    --cc=ak@suse.de \
    --cc=axboe@suse.de \
    --cc=jlundell@pobox.com \
    --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 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®