Re: badblocks and e2fsck

Anthony Barbachan (barbacha@Hinako.AMBusiness.com)
Wed, 14 Oct 1998 20:52:54 -0400

The problem lies in the fact that badblocks is not integrated very well with
e2fsck. e2fsck calls badblocks to get a list of the bad blocks on a device
but does not give it a list of the known ones so badblocks rechecks the
known bad block again, even worse this means that sometimes a bad block get
remarked good because it just happens to have passed the last bad blocks
check.

-----Original Message-----
From: Jerry Geis <geisj@pagestation.com>
To: linux <linux-kernel@vger.rutgers.edu>
Date: Wednesday, October 14, 1998 4:36 AM
Subject: badblocks and e2fsck

>Gents
>
>It appears that my disk has some badblocks. I
>am attempting to run 'e2fsck -cf /dev/hda4'
>to clear it up. It says that it is detecting
>them and fixing them but then I run the same
>command and it finds the same ones again.
>Is this normal? I would think it would already
>now the sector is bad and not try it.
>
>Anyway, it appears it is not fixing the problem.
>
>AM I mising something?
>
>I run 2.0.36pre14 slackware 3.5
>
>Please CC me directly.
>
>Jerry Geis
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.rutgers.edu
>Please read the FAQ at http://www.tux.org/lkml/
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/