Re: [PATCH] btrfs: Better csum error message for data csum mismatch

2017-02-10 Thread David Sterba
On Thu, Feb 09, 2017 at 10:45:06AM +0800, Qu Wenruo wrote: > The original csum error message only outputs inode number, offset, check > sum and expected check sum. > > However no root objectid is outputted, which sometimes makes debugging > quite painful under multi-subvolume case (including

[PATCH] btrfs: Better csum error message for data csum mismatch

2017-02-08 Thread Qu Wenruo
The original csum error message only outputs inode number, offset, check sum and expected check sum. However no root objectid is outputted, which sometimes makes debugging quite painful under multi-subvolume case (including relocation). Also the checksum output is decimal, which seldom makes

[PATCH] btrfs: Better csum error message for data csum mismatch

2017-02-08 Thread Qu Wenruo
The original csum error message only outputs inode number, offset, check sum and expected check sum. However no root objectid is outputted, which sometimes makes debugging quite painful under multi-subvolume case (including relocation). Also the checksum output is decimal, which seldom makes

[PATCH] btrfs: Better csum error message for data csum mismatch

2017-02-06 Thread Qu Wenruo
The original csum error message only outputs inode number, offset, check sum and expected check sum. However no root objectid is outputted, which sometimes makes debugging quite painful under multi-subvolume case (including relocation). Also the checksum output is decimal, which seldom makes