Btrfs-progs: fsck: handle case that we can not lookup extent info
authorWang Shilong <wangsl.fnst@cn.fujitsu.com>
Thu, 6 Mar 2014 05:54:00 +0000 (13:54 +0800)
committerChris Mason <clm@fb.com>
Fri, 21 Mar 2014 13:23:39 +0000 (06:23 -0700)
commit8d2359c8d9419be10e3af75f426e984df3d2e020
treebf65dac341701a4b875b76ba78eba730ae865fb9
parent706a90b1223594b95898e3e0355b42354b238669
Btrfs-progs: fsck: handle case that we can not lookup extent info

Previously, --init-extent-tree works just because btrfs_lookup_extent_info()
blindly return 0, and this make it work if there are not any *FULL BACKREF*
mode in broken filesystem.

It is just a coincidence that --init-extent-tree option works, let's
do it in the right way firstly.

For now, we have not supported to rebuild extent tree if there are
any *FULL BACKREF* mode which means if there are snapshots with broken
filesystem, avoid using --init-extent-tree option now.

Signed-off-by: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
Signed-off-by: David Sterba <dsterba@suse.cz>
Signed-off-by: Chris Mason <clm@fb.com>
cmds-check.c
extent-tree.c