btrfs is clever enough to figure out which devices constitute the sprout
fs even without specifying them explicitly with -o device. Additionally,
explicitly settings the devices via -o device reduces coverage of the
test since it didn't detect breakage a local change introduced. Without
-o device instead this breakage was detected.
Signed-off-by: Nikolay Borisov <nborisov@xxxxxxxx>
---
tests/btrfs/162 | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/tests/btrfs/162 b/tests/btrfs/162
index 7f119be057b7..ff3c50b1be54 100755
--- a/tests/btrfs/162
+++ b/tests/btrfs/162
@@ -69,11 +69,10 @@ create_sprout_seed()
create_next_sprout()
{
- run_check _mount -o device=$dev_seed $dev_sprout_seed $SCRATCH_MNT
+ run_check _mount $dev_sprout_seed $SCRATCH_MNT
_run_btrfs_util_prog device add -f $dev_sprout $SCRATCH_MNT
_scratch_unmount
- run_check _mount -o device=$dev_seed,device=$dev_sprout_seed \
- $dev_sprout $SCRATCH_MNT
+ run_check _mount $dev_sprout $SCRATCH_MNT
echo -- sprout --
od -x $SCRATCH_MNT/foobar
}
--
2.17.1
