Messages in this thread | | | Date | Sun, 29 Jun 2014 17:04:28 -0400 | From | Theodore Ts'o <> | Subject | Re: ext4: total breakdown on USB hdd, 3.0 kernel |
| |
On Sun, Jun 29, 2014 at 10:25:16PM +0200, Pavel Machek wrote: > > One more thing that I noticed: fsck notices bad checksum on inode, and > then offers to fix the checksum with 'y' being the default. If there's > trash in the inode, that will just induce more errors. (Including > potentially doubly-linked blocks?) Would it make more sense to clear > the inodes with bad checksums?
Metadata checksums aren't in e2fsprogs 1.41 or 1.42. It will be in the to-be-released e2fsprogs 1.43, and yes, we need to change things so that the default answer is to zero the inode. We didn't do that initially because we were more suspicious of the new metadata checksum code in the kernel and e2fsprogs than we were of hardware faults. :-)
Cheers,
- Ted
| |