On Tue, Jun 28, 2016 at 9:58 AM, Francesco Turco <ftu...@fastmail.fm> wrote: > When trying to repair a btrfs root filesystem I get the following error > message: > > # losetup -f /home/fturco/Buffer/root-20160616.img > # btrfs check --repair /dev/loop0 > enabling repair mode > warning, device 4 is missing > Checking filesystem on /dev/loop0 > UUID: 34fb5b58-f50f-47c3-a5b8-91d81a30eade > checking extents > Unable to find block group for 0 > extent-tree.c:289: find_search_start: Assertion `1` failed.
Well it probably shouldn't crash but the question is why is device 4 missing? We have no information what version of btrfs-progs or kernel is used, or what the layout of this volume is: how many devices, what's the profile breakdown, etc. Are you attempting to fix a degraded volume and are the minimum number of devices present? Btrfs fi show would be useful for this. If it's relatively recent version of btrfs-progs then I'd file a bug just because it shouldn't crash, it should give some sort of coherent message about why it can't proceed. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
