When we're doing the second online scrub (to figure out if the repair
did any good) we shouldn't let that second scrub preen the filesystem in
any way. If scrub finds things it can't/won't preen that turns into a
nonzero return code which gets reported (incorrectly) as a failure.
Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx>
---
common/fuzzy | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/fuzzy b/common/fuzzy
index 7a4b03a..87f7acc 100644
--- a/common/fuzzy
+++ b/common/fuzzy
@@ -275,7 +275,7 @@ __scratch_xfs_fuzz_field_test() {
# which scrub doesn't know how to fix.
echo "++ Online scrub"
if [ "$1" != "sb 0" ]; then
- _scratch_scrub -e continue 2>&1
+ _scratch_scrub -n -e continue 2>&1
res=$?
test $res -ne 0 && \
(>&2 echo "online re-scrub ($res) with ${field} = ${fuzzverb}.")
--
To unsubscribe from this list: send the line "unsubscribe fstests" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
