On Sun, Jul 06, 2014 at 11:37:11PM +0200, Pavel Machek wrote: > > Well, when I got report about hw problems, badblocks -c was my first > instinct. On the usb hdd, the most errors were due to 3.16-rc1 kernel > bug, not real problems. The problem is with modern disk drives, this is a *wrong* instinct. That's my point. In general, trying to mess with the bad blocks list in the ext2/3/4 file system is just not the right thing to do with modern disk drives. That's because with modern disk drives, the hard drives will do bad block remapping. Basically, with modern disks, if the HDD has a hard ECC error, it will return an error --- but if you write to the sector, it will either rewrite onto that location on the platter, or if that part of the platter is truly gone, it will remap to the bad block spare pool. So telling the disk to never use that block again isn't going to be the right answer. The badblocks approach to dealing with hardware problems made sense back when we had IDE disks. But that's been over a decade ago. These days, it's horribly obsolete. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
