On Fri, Aug 01, 2014 at 11:12:34AM -0700, Darrick J. Wong wrote: > From: Darrick J. Wong <darrick.wong@xxxxxxxxxx> > > Add a new behavior flag to the inode scan functions; when specified, > this flag will do some simple sanity checking of entire inode table > blocks. If all the checksums are ok, we can skip checksum > verification on individual inodes later on. If more than half of the > inodes look "insane" (bad extent tree root or checksum failure) then > ext2fs_get_next_inode_full() can return a special status code > indicating that what's in the buffer is probably garbage. > > When e2fsck' inode scan encounters the 'inode is garbage' return code > it'll offer to zap the inode straightaway instead of trying to recover > anything. This replaces the previous behavior of asking to zap > anything with a checksum error (strict_csum). > > Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxx> Applied, thanks!! - 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
