Messages in this thread | | | From | (Matthias Urlichs) | Subject | Re: badblocks and e2fsck | Date | 30 Oct 1998 15:15:00 +0100 |
| |
ptb@it.uc3m.es writes: > > > 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 > > What's wrong with > dumpe2fs blah | grep /^Bad/ | sed -e 's/.*: //' > badlist > e2fsck -f -l badlist blah > What's wrong is that you're not actually checking for new bad blocks that way, and e2fsck already obeys the existing bad block list.
Moreover, badblocks doesn't listen to any existing bad block list, which is a pain in the ass when your hard disk tends to crash and burn when it hits the offending sector. (You can get there if the HD's firmware is crappy and you're foolish enough to do a low-level reformat which ignores the existing bad block list *on*disk*, i.e. this happens even with disks that aren't going to fall over and play dead tomorrow anyway.)
-- Matthias Urlichs | noris network GmbH | smurf@noris.de | ICQ: 20193661 The quote was selected randomly. Really. | http://www.noris.de/~smurf/ -- The only difference in the game of love over the last few thousand years is that they've changed trumps from clubs to diamonds. --The Indianapolis Star
- 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/
| |