On Sat, 24 May 2008 23:45:24 +0800 "Peter Teoh" <htmldeveloper@xxxxxxxxx> wrote: > Just out of curiosity.....when OS build the list of inodes....it scan > and identify all the corrupted blocks, and so the outcome of mkfs will > be all the uncorrupted blocks on the harddisk - right? No, mkfs just writes and hopes that the blocks it wrote can be read in again later. I do not believe it does any testing by default. > so possibly there are many other corrupted blocks on the harddisk Yes. > Is there any tools that can allow me to see / identify all these > corrupted blocks? badblocks Read the man page carefully, you probably want the "-n" option. > And given that there are many corrupted blocks, when I do a mkfs to > create a new filesystem, all the corrupted blocks will be marked away, > and therefore the new filesystem should have less total space, but > guaranteed NOT TO HAVE any corrupted blocks, right? No, mkfs does not scan the disk for bad blocks by default. -- All rights reversed. -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
