mirror of
https://github.com/kdave/btrfs-progs
synced 2025-04-11 03:31:17 +00:00
b20f94e984
As seem in issue #192, this test can fail from time to time. The issue happens when a mount is issued before the new device is processed by systemd-udevd, as we can see by the og bellow: [ 2346.028809] BTRFS: device fsid 593e23af-a7e6-4360-b16a-229f415de697 devid 1 transid 6 /dev/loop10 scanned by systemd-udevd (3418) [ 2346.265401] BTRFS info (device loop10): found metadata UUID change in progress flag, clearing [ 2346.272474] BTRFS info (device loop10): disk space caching is enabled [ 2346.277472] BTRFS info (device loop10): has skinny extents [ 2346.281840] BTRFS info (device loop10): flagging fs with big metadata feature [ 2346.308428] BTRFS error (device loop10): devid 2 uuid cde07de6-db7e-4b34-909e-d3db6e7c0b06 is missing [ 2346.315363] BTRFS error (device loop10): failed to read the system array: -2 [ 2346.329887] BTRFS error (device loop10): open_ctree failed failed: mount /dev/loop10 /home/marcos/git/suse/btrfs-progs/tests//mnt test failed for case 034-metadata-uuid make: *** [Makefile:401: test-misc] Error 1 [ 2346.666865] BTRFS: device fsid 593e23af-a7e6-4360-b16a-229f415de697 devid 2 transid 5 /dev/loop11 scanned by systemd-udevd (3422) [ 2346.853233] BTRFS: device fsid 1c2debeb-e829-4d6b-84df-aa7c5d246fd5 devid 1 transid 7 /dev/loop6 scanned by systemd-udevd (3418) A few moments after the test failed systemd-udevd processed the new device (registered the new device under btrfs). This can be tested by executing a mount after the test failed, resulting in a successful mount: $ mount /dev/loop10 /mnt [ 2398.955254] BTRFS info (device loop10): found metadata UUID change in progress flag, clearing [ 2398.959416] BTRFS info (device loop10): disk space caching is enabled [ 2398.962483] BTRFS info (device loop10): has skinny extents [ 2398.965070] BTRFS info (device loop10): flagging fs with big metadata feature [ 2399.012617] BTRFS info (device loop10): enabling ssd optimizations [ 2399.022375] BTRFS info (device loop10): checking UUID tree This problem can be avoided is we execute "udevadm settle" before the mount is executed. Issue: #192 Reviewed-by: Nikolay Borisov <nborisov@suse.com> Reviewed-by: Su Yue <Damenly_Su@gmx.com> Signed-off-by: Marcos Paulo de Souza <mpdesouza@suse.com> Signed-off-by: David Sterba <dsterba@suse.com> |
||
|---|---|---|
| .. | ||
| 001-btrfstune-features | ||
| 002-uuid-rewrite | ||
| 003-zero-log | ||
| 004-shrink-fs | ||
| 005-convert-progress-thread-crash | ||
| 006-image-on-missing-device | ||
| 007-subvolume-sync | ||
| 008-leaf-crossing-stripes | ||
| 009-subvolume-sync-must-wait | ||
| 010-convert-delete-ext2-subvol | ||
| 011-delete-missing-device | ||
| 012-find-root-no-result | ||
| 013-subvolume-sync-crash | ||
| 014-filesystem-label | ||
| 015-dump-super-garbage | ||
| 016-send-clone-src | ||
| 017-recv-stream-malformatted | ||
| 018-recv-end-of-stream | ||
| 019-receive-clones-on-mounted-subvol | ||
| 020-fix-superblock-corruption | ||
| 021-image-multi-devices | ||
| 022-filesystem-du-on-empty-subvol | ||
| 023-device-usage-with-missing-device | ||
| 024-inspect-internal-rootid | ||
| 025-zstd-compression | ||
| 026-image-non-printable-chars | ||
| 027-subvol-list-deleted-toplevel | ||
| 028-superblock-recover | ||
| 029-send-p-different-mountpoints | ||
| 030-missing-device-image | ||
| 031-qgroup-parent-child-relation | ||
| 032-bad-item-ptr | ||
| 033-filename-length-limit | ||
| 034-metadata-uuid | ||
| 035-receive-common-mount-point-prefix | ||
| 036-receive-dump-invalid-stream | ||
| 037-fi-show-on-new-file | ||
| 038-backup-root-corruption | ||