Zheng Liu <gnehzuil.liu@xxxxxxxxx> writes: > My idea is to let file system can ignore the currurted block. Namely, > when we meet a currupted block, we will track it as bad block in bad > block inode and find another block to save data. This currupted block > will never be used. The first step in my mind is to detect a currpted > block and mark it as bad block. After reading the thread and Darrick's > original patch, I think Darrick's patch is a good start. I think it's important to call out the exact failure scenario you're trying to address. For hard disks, if you get a read error, it can typically be recovered by re-writing the block. I imagine this is what fsck would be doing for metadata repair. So, I'm not at all sure why you'd want to track bad blocks in the file system itself. Could you elaborate, please? Cheers, Jeff -- 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
