Re: [PATCH 06/19] e2fsck: try to salvage extent blocks with bad checksums

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Aug 01, 2014 at 11:12:21AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@xxxxxxxxxx>
> 
> Remove the code that would zap an extent block immediately if the
> checksum failed (i.e. strict_csums).  Instead, we'll only do that if
> the extent block header shows obvious structural problems; if the
> header checks out, then we'll iterate the block and see if we can
> recover some extents.
> 
> Requires a minor modification to ext2fs_extent_get such that the
> extent block will be returned in the buffer even if the return code
> indicates a checksum error.  This brings its behavior in line with
> the rest of libext2fs.
> 
> Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx>

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




[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux