xfs
[Top] [All Lists]

bad block (was: Could IDE UDMA corruption be kgcc related?)

To: stimits@xxxxxxxxxx
Subject: bad block (was: Could IDE UDMA corruption be kgcc related?)
From: Eric Sandeen <sandeen@xxxxxxx>
Date: Wed, 04 Jul 2001 21:36:54 -0500
Cc: linux-xfs <linux-xfs@xxxxxxxxxxx>
References: <3B42BC57.504A20FF@ch.sauter-bc.com> <3B437D88.3B272793@idcomm.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
"D. Stimits" wrote:

> Probably someone has mentioned this already, I'm curious about what to
> use to check for bad blocks? Since fsck.xfs just returns, and I'm not
> sure if the blockmap in the man page for xfs_repair refers to the same
> thing as checking for bad blocks and marking them, what is the
> specifically recommended way to check for bad blocks on an XFS
> partition? Is the filesystem itself able to work around bad blocks
> (especially if the drive is degrading and new bad blocks are appearing)?
> If so, does it log a message to let the admin know of a degrading drive?

XFS doesn't have any bad-block tracking.  See the archives for a couple
discussions about this, but the consensus seems to be that drives are
_always_ degrading, and bad blocks are _always_ appearing - it's just
that the drive handles this internally, and rearranges things to protect
the data.  By the time the user actually sees bad blocks, the drive can
no longer cope, and the game is pretty much over.

Search for "ucsc-smartsuite" for a tool that will monitor the drive's
coping ability, and warn the admin if things are getting too bad,
hopefully before data is lost...

-Eric

-- 
Eric Sandeen      XFS for Linux     http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx   SGI, Inc.

<Prev in Thread] Current Thread [Next in Thread>