|
|||||||||||
|
Re: e2fsck -c to check for bad blocks
From: Christopher Zimmermann <madroach(at)zakweb.de>
Date: Wed Feb 13 2008 - 12:23:30 EST
> I gather one can use the e2fsck with -c option to have it call This option causes e2fsck to use badblocks(8) program to do a read-only scan of the device in order to find any bad blocks. If any bad blocks are found, they are added to the bad block inode to prevent them from being allocated to a file or directory. If this option is specified twice, then the bad block scan will be done using a non-destructive read-write test. > Yes, it does fix it. "they are added to the bad block inode" > 2. If badblocks is non-destructive, why does the targeted filesystem Does it have to be? What does -f say? fsck always complains if the fs is mounted. Note that in general it is not safe to run e2fsck on mounted filesystems. The only exception is if the -n option is specified, and -c, -l, or -L options are not specified. However, even if it is safe to do so, the results printed by e2fsck are not valid if the filesystem is mounted. If e2fsck asks whether or not you should check a filesystem which is mounted, the only correct answer is âânoââ. Only experts who really know what they are doing should consider answering this question in any other way. Badblocks may be non-destructive, but adding the found blocks to the inode may be bad. You don't know what fsck will do other than running badblocks. > correct. > correct. > -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.orgReceived on Wed Feb 13 12:24:16 2008 This archive was generated by hypermail 2.1.8 : Fri Mar 14 2008 - 19:27:58 EDT |
||||||||||
|
|||||||||||