Re: [PATCH] btrfs-progs: print the csum length in debug-tree

2017-09-01 Thread David Sterba
On Fri, Aug 25, 2017 at 04:48:43PM +0300, Nikolay Borisov wrote: > > > On 25.08.2017 16:13, jo...@toxicpanda.com wrote: > > From: Josef Bacik > > > > While looking at a log of a corrupted fs I needed to verify we were > > missing csums for a given range. Make this easier by printing out how >

Re: [PATCH] btrfs-progs: print the csum length in debug-tree

2017-08-25 Thread Josef Bacik
On Fri, Aug 25, 2017 at 04:48:43PM +0300, Nikolay Borisov wrote: > > > On 25.08.2017 16:13, jo...@toxicpanda.com wrote: > > From: Josef Bacik > > > > While looking at a log of a corrupted fs I needed to verify we were > > missing csums for a given range. Make this easier by printing out how >

Re: [PATCH] btrfs-progs: print the csum length in debug-tree

2017-08-25 Thread Nikolay Borisov
On 25.08.2017 16:13, jo...@toxicpanda.com wrote: > From: Josef Bacik > > While looking at a log of a corrupted fs I needed to verify we were > missing csums for a given range. Make this easier by printing out how > many bytes a csum extent item represents when using btrfs_debug_tree. > > Sign

[PATCH] btrfs-progs: print the csum length in debug-tree

2017-08-25 Thread josef
From: Josef Bacik While looking at a log of a corrupted fs I needed to verify we were missing csums for a given range. Make this easier by printing out how many bytes a csum extent item represents when using btrfs_debug_tree. Signed-off-by: Josef Bacik --- print-tree.c | 10 -- 1 file