RepoMirrors
/
btrfs-progs
mirror of https://github.com/kdave/btrfs-progs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
btrfs-progs/tests/misc-tests/051-warning-rw-subvol-recei.../test.sh

49 lines
1.6 KiB
Bash
Raw Normal View History

btrfs-progs: subvol show: print a warning with rw and receive_uuid Add a slightly more convenient way to identify the subvolumes with bad combination of flags and received uuid. Signed-off-by: David Sterba <dsterba@suse.com>
2021-10-07 16:33:27 +00:00
#!/bin/bash
# Look for warning about read-write subvolume with received_uuid set, on a crafted
# image
btrfs-progs: tests: add protection against running out of test suite Executing the script inside the directories as './test.sh' is not supposed to work but could happen accidentally. With an exit after attempting to source the we can fix that. Signed-off-by: David Sterba <dsterba@suse.com>
2023-04-19 15:08:41 +00:00
source "$TEST_TOP/common" || exit
btrfs-progs: subvol show: print a warning with rw and receive_uuid Add a slightly more convenient way to identify the subvolumes with bad combination of flags and received uuid. Signed-off-by: David Sterba <dsterba@suse.com>
2021-10-07 16:33:27 +00:00
setup_root_helper
prepare_test_dev
btrfs-progs: fix read-write subvol and received_uuid flags check There's a report that a read-only subvolume with a received_uuid set emits the warning in command 'btrfs subvolume show', which is obviously wrong. The reason is that there are different types of root item flags, depending on how we read them. The check in cmd_subvol_show uses the ioctl GET_SUBVOL_INFO and the appropriate flag is raw BTRFS_ROOT_SUBVOL_RDONLY (0x1), while there's another SUBVOL_GETFLAGS that maps the flags and the raw value is different (BTRFS_SUBVOL_RDONLY, 0x2). Due to this the warning was issued. Fix that by using the right flag constant. The test has been extended to check for all combinations of read-write and received_uuid. Issue: #419 Signed-off-by: David Sterba <dsterba@suse.com>
2021-11-01 22:33:26 +00:00
ORIG_TEST_DEV="$TEST_DEV"
btrfs-progs: subvol show: print a warning with rw and receive_uuid Add a slightly more convenient way to identify the subvolumes with bad combination of flags and received uuid. Signed-off-by: David Sterba <dsterba@suse.com>
2021-10-07 16:33:27 +00:00
TEST_DEV=$(extract_image "subvol-rw-recv.img")
run_check_mount_test_dev
if ! run_check_stdout $SUDO_HELPER "$TOP/btrfs" subvolume show "$TEST_MNT/subvol1" |
grep -q "WARNING.*received_uuid"; then
_fail "no warning found"
fi
if run_check_stdout $SUDO_HELPER "$TOP/btrfs" subvolume show "$TEST_MNT/snap1" |
grep -q "WARNING.*received_uuid"; then
_fail "unexpected warning"
fi
run_check_umount_test_dev
rm -- "$TEST_DEV"
btrfs-progs: fix read-write subvol and received_uuid flags check There's a report that a read-only subvolume with a received_uuid set emits the warning in command 'btrfs subvolume show', which is obviously wrong. The reason is that there are different types of root item flags, depending on how we read them. The check in cmd_subvol_show uses the ioctl GET_SUBVOL_INFO and the appropriate flag is raw BTRFS_ROOT_SUBVOL_RDONLY (0x1), while there's another SUBVOL_GETFLAGS that maps the flags and the raw value is different (BTRFS_SUBVOL_RDONLY, 0x2). Due to this the warning was issued. Fix that by using the right flag constant. The test has been extended to check for all combinations of read-write and received_uuid. Issue: #419 Signed-off-by: David Sterba <dsterba@suse.com>
2021-11-01 22:33:26 +00:00
TEST_DEV="$ORIG_TEST_DEV"
run_check_mkfs_test_dev
run_check_mount_test_dev
run_check $SUDO_HELPER "$TOP/btrfs" subvolume create "$TEST_MNT/subvol1"
if run_check_stdout $SUDO_HELPER "$TOP/btrfs" subvolume show "$TEST_MNT/subvol1" |
grep -q "WARNING.*received_uuid"; then
_fail "unexpected warning"
fi
run_check $SUDO_HELPER "$TOP/btrfs" subvolume snapshot -r "$TEST_MNT/subvol1" "$TEST_MNT/snap1"
if run_check_stdout $SUDO_HELPER "$TOP/btrfs" subvolume show "$TEST_MNT/snap1" |
grep -q "WARNING.*received_uuid"; then
_fail "unexpected warning"
fi
btrfs-progs: tests: use _mktemp_local for temporary files Signed-off-by: David Sterba <dsterba@suse.com>
2022-09-15 14:02:09 +00:00
btrfs-progs: fix read-write subvol and received_uuid flags check There's a report that a read-only subvolume with a received_uuid set emits the warning in command 'btrfs subvolume show', which is obviously wrong. The reason is that there are different types of root item flags, depending on how we read them. The check in cmd_subvol_show uses the ioctl GET_SUBVOL_INFO and the appropriate flag is raw BTRFS_ROOT_SUBVOL_RDONLY (0x1), while there's another SUBVOL_GETFLAGS that maps the flags and the raw value is different (BTRFS_SUBVOL_RDONLY, 0x2). Due to this the warning was issued. Fix that by using the right flag constant. The test has been extended to check for all combinations of read-write and received_uuid. Issue: #419 Signed-off-by: David Sterba <dsterba@suse.com>
2021-11-01 22:33:26 +00:00
run_check $SUDO_HELPER mkdir "$TEST_MNT/recv"
btrfs-progs: tests: use _mktemp_local for temporary files Signed-off-by: David Sterba <dsterba@suse.com>
2022-09-15 14:02:09 +00:00
_mktemp_local send.stream
btrfs-progs: fix read-write subvol and received_uuid flags check There's a report that a read-only subvolume with a received_uuid set emits the warning in command 'btrfs subvolume show', which is obviously wrong. The reason is that there are different types of root item flags, depending on how we read them. The check in cmd_subvol_show uses the ioctl GET_SUBVOL_INFO and the appropriate flag is raw BTRFS_ROOT_SUBVOL_RDONLY (0x1), while there's another SUBVOL_GETFLAGS that maps the flags and the raw value is different (BTRFS_SUBVOL_RDONLY, 0x2). Due to this the warning was issued. Fix that by using the right flag constant. The test has been extended to check for all combinations of read-write and received_uuid. Issue: #419 Signed-off-by: David Sterba <dsterba@suse.com>
2021-11-01 22:33:26 +00:00
run_check $SUDO_HELPER "$TOP/btrfs" send -f send.stream "$TEST_MNT/snap1"
run_check $SUDO_HELPER "$TOP/btrfs" receive -f send.stream -m "$TEST_MNT" "$TEST_MNT/recv"
if run_check_stdout $SUDO_HELPER "$TOP/btrfs" subvolume show "$TEST_MNT/recv/snap1" |
grep -q "WARNING.*received_uuid"; then
_fail "unexpected warning"
fi
run_check_umount_test_dev
rm -- send.stream