diff options
| author | Wang Shilong <wangsl.fnst@cn.fujitsu.com> | 2014-03-06 13:54:00 +0800 |
|---|---|---|
| committer | Chris Mason <clm@fb.com> | 2014-03-21 06:23:39 -0700 |
| commit | 8d2359c8d9419be10e3af75f426e984df3d2e020 (patch) | |
| tree | bf65dac341701a4b875b76ba78eba730ae865fb9 /extent-tree.c | |
| parent | 706a90b1223594b95898e3e0355b42354b238669 (diff) | |
| download | btrfs-progs-8d2359c8d9419be10e3af75f426e984df3d2e020.tar.gz | |
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>
Diffstat (limited to 'extent-tree.c')
| -rw-r--r-- | extent-tree.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/extent-tree.c b/extent-tree.c index 7860d1d..7979457 100644 --- a/extent-tree.c +++ b/extent-tree.c @@ -1560,7 +1560,7 @@ again: *flags = extent_flags; out: btrfs_free_path(path); - return 0; + return ret; } int btrfs_set_block_flags(struct btrfs_trans_handle *trans, |