On 2018年03月26日 21:59, Nikolay Borisov wrote: > Verify that if we have an otherwise clean filesystem, containging collided > DIR_ITEM, btrfs check lowmem's mode can correctly handle those and not produce > any false positives. > > This if fixed by commit titled: > > "btrfs-progs: Fix DIR_ITEM checking in lowmem" > > Signed-off-by: Nikolay Borisov <nbori...@suse.com>
Reviewed-by: Qu Wenruo <w...@suse.com> Thanks, Qu > --- > .../031-lowmem-collission-dir-items/test.sh | 23 > ++++++++++++++++++++++ > 1 file changed, 23 insertions(+) > create mode 100755 tests/fsck-tests/031-lowmem-collission-dir-items/test.sh > > diff --git a/tests/fsck-tests/031-lowmem-collission-dir-items/test.sh > b/tests/fsck-tests/031-lowmem-collission-dir-items/test.sh > new file mode 100755 > index 000000000000..fa0b88af0557 > --- /dev/null > +++ b/tests/fsck-tests/031-lowmem-collission-dir-items/test.sh > @@ -0,0 +1,23 @@ > +#!/bin/bash > +# Ensure that running btrfs check on a fs which has name collisions of files > +# doesn't result in false positives. This test is specifically targeted at > +# lowmem mode. > +source "$TEST_TOP/common" > + > +check_prereq btrfs > +check_prereq mkfs.btrfs > + > +setup_root_helper > +prepare_test_dev > + > +run_check $SUDO_HELPER "$TOP/mkfs.btrfs" -f "$TEST_DEV" > +run_check_mount_test_dev > + > +# Create 2 files whose names collide > +run_check $SUDO_HELPER touch > "$TEST_MNT/5ab4e206~~~~~~~~XVT1U3ZF647YS2PD4AKAG826" > +run_check $SUDO_HELPER touch > "$TEST_MNT/5ab4e26a~~~~~~~~AP1C3VQBE79IJOTVOEZIR9YU" > + > +run_check_umount_test_dev > + > +# The fs is clean so lowmem shouldn't produce any warnings > +run_check "$TOP/btrfs" check --readonly "$TEST_DEV" >
signature.asc
Description: OpenPGP digital signature
