btrfs-progs: skip extent rebuild test if no testdev
It is highly obnoxious to have to go put in a testdev when all you really want is to run the quick image tests. Make this part optional so if we don't have a testdev specified we just don't run that particular test. Thanks, Signed-off-by: Josef Bacik <jbacik@fb.com> Signed-off-by: David Sterba <dsterba@suse.cz>
This commit is contained in:
parent
d5fd05a773
commit
935457f164
|
@ -24,10 +24,6 @@ run_check()
|
||||||
|
|
||||||
rm -f $RESULT
|
rm -f $RESULT
|
||||||
|
|
||||||
if [ -z $TEST_DEV ] || [ -z $TEST_MNT ];then
|
|
||||||
_fail "please set TEST_DEV and TEST_MNT"
|
|
||||||
fi
|
|
||||||
|
|
||||||
# test rely on corrupting blocks tool
|
# test rely on corrupting blocks tool
|
||||||
run_check make btrfs-corrupt-block
|
run_check make btrfs-corrupt-block
|
||||||
|
|
||||||
|
@ -45,6 +41,11 @@ do
|
||||||
run_check $here/btrfsck test.img
|
run_check $here/btrfsck test.img
|
||||||
done
|
done
|
||||||
|
|
||||||
|
if [ -z $TEST_DEV ] || [ -z $TEST_MNT ];then
|
||||||
|
echo " [NOTRUN] extent tree rebuild"
|
||||||
|
exit 0
|
||||||
|
fi
|
||||||
|
|
||||||
# test whether fsck can rebuild a corrupted extent tree
|
# test whether fsck can rebuild a corrupted extent tree
|
||||||
test_extent_tree_rebuild()
|
test_extent_tree_rebuild()
|
||||||
{
|
{
|
||||||
|
|
Loading…
Reference in New Issue