search for: ca611db

...ing chunk > tree. > --- > core/fs/btrfs/btrfs.c | 52 +++++++++++++++++++++++++++++++++++---------------- > core/fs/btrfs/btrfs.h | 2 ++ > 2 files changed, 38 insertions(+), 16 deletions(-) > > diff --git a/core/fs/btrfs/btrfs.c b/core/fs/btrfs/btrfs.c > index 53e1105..ca611db 100644 > --- a/core/fs/btrfs/btrfs.c > +++ b/core/fs/btrfs/btrfs.c > @@ -371,16 +386,21 @@ static void btrfs_read_chunk_tree(struct fs_info *fs) > search_tree(fs, bfs->sb.chunk_root, &search_key, &path); > do { >...

..._key multiple times. Set it before parsing chunk tree. --- core/fs/btrfs/btrfs.c | 52 +++++++++++++++++++++++++++++++++++---------------- core/fs/btrfs/btrfs.h | 2 ++ 2 files changed, 38 insertions(+), 16 deletions(-) diff --git a/core/fs/btrfs/btrfs.c b/core/fs/btrfs/btrfs.c index 53e1105..ca611db 100644 --- a/core/fs/btrfs/btrfs.c +++ b/core/fs/btrfs/btrfs.c @@ -81,7 +81,8 @@ static int btrfs_comp_chunk_map(struct btrfs_chunk_map_item *m1, } /* insert a new chunk mapping item */ -static void insert_map(struct fs_info *fs, struct btrfs_chunk_map_item *item) +static void insert_chunk_item...

The current btrfs support did not handled multiple stripes stored in chunk items, hence skipping the physical addresses that were needed to do the mapping. Besides, the chunk tree may contain DEV_ITEM keys which store information on all of the underlying block devices, so we must skip them instead of finishing lookup. The bug was reproduced with btrfs-progs v4.2.2. Cc: Gene Cumm <gene.cumm