Re: "Unknown code" error when enabling metadata_csum on ext4 raid1 device

[Theodore Ts'o <tytso@mit.edu>]

On Wed, Aug 01, 2012 at 03:19:35PM +0800, Zheng Liu wrote:
> Subject: [PATCH] tune2fs: clear error code before rewriting directory when metadata_csum enabled
> 
> From: Zheng Liu <wenqing.lz@taobao.com>
> 
> When we enable metadata_csum feature in tune2fs, all inodes need to be rewrited
> to calculate checksum.  In this process, the inode that has been removed also
> needs to calculate checksum, but the extent tree in these inodes has been clear.
> Thus, we cannot read any extents, and an 'EXT2_ET_EXTENT_NO_NEXT' error is
> returned back.  But in this condition error code in rewrite_dir_context doesn't
> be initialized, and it causes an unknown error.

Thanks, I've merged this into my e2fsprogs checksum branch.

I've promoted all of the metadata checksum patches in e2fsprogs into
the next branch.  

At that point I'll strongly suggest that people use the development
branch (currently the next branch, but in the next or two, the master
branch) of e2fsprogs.  For the kernel, for now I suggest using the
v3.5 kernel with the ext4_for_linus (commit 03179fe92318) from the
ext4.git tree merged in.  Hopefully the necessary bug fix commits will
be in the v3.5.1 kernel, but the 3.5.y series hasn't been released
yet.

						- Ted