Use $DUMPE2FS in resize tests to be sure it's testing the in-tree dumpe2fs, not the system dumpe2fs (which may not even be there...) Signed-off-by: Eric Sandeen <sandeen@xxxxxxxxxx> --- (somehow I thought I had sent this, or something similar, before ... can't find it, oh well!) diff --git a/tests/scripts/resize_test b/tests/scripts/resize_test index 0633e0c..dfd45ac 100755 --- a/tests/scripts/resize_test +++ b/tests/scripts/resize_test @@ -67,7 +67,7 @@ fi echo $FSCK -fy $TMPFILE >> $LOG 2>&1 if ! $FSCK -fy $TMPFILE >> $LOG 2>&1 then - dumpe2fs $TMPFILE >> $LOG + $DUMPE2FS $TMPFILE >> $LOG return 1 fi @@ -97,7 +97,7 @@ fi echo $FSCK -fy $TMPFILE >> $LOG 2>&1 if ! $FSCK -fy $TMPFILE >> $LOG 2>&1 then - dumpe2fs $TMPFILE >> $LOG + $DUMPE2FS $TMPFILE >> $LOG return 1 fi @@ -122,7 +122,7 @@ fi echo $FSCK -fy $TMPFILE >> $LOG 2>&1 if ! $FSCK -fy $TMPFILE >> $LOG 2>&1 then - dumpe2fs $TMPFILE >> $LOG + $DUMPE2FS $TMPFILE >> $LOG return 1 fi @@ -147,7 +147,7 @@ fi echo $FSCK -fy $TMPFILE >> $LOG 2>&1 if ! $FSCK -fy $TMPFILE >> $LOG 2>&1 then - dumpe2fs $TMPFILE >> $LOG + $DUMPE2FS $TMPFILE >> $LOG return 1 fi -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
