Thank you Rik... On Sun, May 25, 2008 at 12:15 AM, Rik van Riel <riel@xxxxxxxxxxx> wrote: > 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. > thank you for the summary....i am looking for codes that does that.....but got no time to read/understand everything of mkfs...... >> 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 > wow...this is amazing.....part of e2fs....found my answer...and really got to start understanding the e2fs package.... > 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. > i always find this amusing....it means that I will be paid if I copied your ideas....or I have to pay you in order that u can copy my ideas.... -- Regards, Peter Teoh -- 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
