mirror of
https://github.com/kdave/btrfs-progs
synced 2024-12-25 15:42:23 +00:00
1faaa874a1
Since a few days the CI started to fail randomly when there were loop devices used in the tests. The mount fails because some device is reported to be missing: $ losetup --show --find /dev/loop3 ... $ mkfs ... ERROR: device scan failed on '/dev/loop3': No such file or directory ... $ mount mount: /home/runner/work/btrfs-progs/btrfs-progs/tests/mnt: wrong fs type, bad option, bad superblock on /dev/loop3, missing codepage or helper program, or other error. $ dmesg ... BTRFS error (device loop0): devid 3 uuid 11d9c345-9527-433e-a024-7102659fa0ee is missing BTRFS error (device loop0): failed to read the system array: -2 BTRFS error (device loop0): open_ctree failed This was reproducible in the "cli" tests, but also happened on a local machine. To fix that wait for all loop devices before mount, the command 'btrfs device ready' should block until that. The convenience helper does that, for any standalone 'mount' used with loop devices this must be done manually. Signed-off-by: David Sterba <dsterba@suse.com> |
||
---|---|---|
.. | ||
001-basic-profiles | ||
002-no-force-mixed-on-small-volume | ||
003-mixed-with-wrong-nodesize | ||
004-rootdir-keeps-size | ||
005-long-device-name-for-ssd | ||
006-partitioned-loopdev | ||
007-mix-nodesize-sectorsize | ||
008-sectorsize-nodesize-combination | ||
009-special-files-for-rootdir | ||
010-minimal-size | ||
011-rootdir-create-file | ||
012-rootdir-no-shrink | ||
013-reserved-1M-for-single | ||
014-rootdir-inline-extent | ||
015-fstree-uuid-otime | ||
016-rootdir-bad-symbolic-link | ||
017-small-backing-size-thin-provision-device | ||
018-multidevice-overflow | ||
019-basic-checksums-mkfs | ||
020-basic-checksums-mount | ||
021-rfeatures-quota-rootdir | ||
022-rootdir-size | ||
023-free-space-tree | ||
024-fst-bitmaps | ||
025-zoned-parallel | ||
026-extent-tree-to-bgt | ||
027-rootdir-inode | ||
028-block-group-tree | ||
029-raid-stripe-tree | ||
030-zoned-rst |