After commit
aaa132777476 ("fstests: per-test dmdust instances") the
dmdust device names are no longer a plain 'dust-test', they now have
a suffix matching '.N', where N is the test's sequence number.
The test cases btrf/142 and btrfs/143 are still using the old device
names, so they fail. Fix this my making them refer to 'dust-test.$seq'
instead of 'dust-test'.
Fixes: aaa132777476 ("fstests: per-test dmdust instances")
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Signed-off-by: Zorro Lang <zlang@kernel.org>
# step 3, 128k dio read (this read can repair bad copy)
echo "step 3......repair the bad copy" >>$seqres.full
-$DMSETUP_PROG message dust-test 0 addbadblock $((physical / 512))
-$DMSETUP_PROG message dust-test 0 enable
+$DMSETUP_PROG message dust-test.$seq 0 addbadblock $((physical / 512))
+$DMSETUP_PROG message dust-test.$seq 0 enable
_btrfs_direct_read_on_mirror $stripe 2 "$SCRATCH_MNT/foobar" 0 128K
# step 3, 128k buffered read (this read can repair bad copy)
echo "step 3......repair the bad copy" >>$seqres.full
-$DMSETUP_PROG message dust-test 0 addbadblock $((physical / 512))
-$DMSETUP_PROG message dust-test 0 enable
+$DMSETUP_PROG message dust-test.$seq 0 addbadblock $((physical / 512))
+$DMSETUP_PROG message dust-test.$seq 0 enable
_btrfs_buffered_read_on_mirror $stripe 2 "$SCRATCH_MNT/foobar" 0 128K