xfs/155: improve logging in this test

If this test fails after a certain number of writes, we should state
the exact number of writes so that we can coordinate with 155.full.
Instead, we state the pre-randomization number, which isn't all that
helpful.

Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Bill O'Donnell <bodonnel@redhat.com>
Signed-off-by: Zorro Lang <zlang@kernel.org>

diff --git a/tests/xfs/155 b/tests/xfs/155
index 25cc84069cc6786b791d5e0fe55916b7f479d0b8..302607b510f6146615b89df07c7999c90ed9f829 100755 (executable)
--- a/tests/xfs/155
+++ b/tests/xfs/155
@@ -63,11 +63,12 @@ done
 
 # If NEEDSREPAIR is still set on the filesystem, ensure that a full run
 # cleans everything up.
+echo "Checking filesystem one last time after $allowed_writes writes." >> $seqres.full
 if _check_scratch_xfs_features NEEDSREPAIR &> /dev/null; then
        echo "Clearing NEEDSREPAIR" >> $seqres.full
        _scratch_xfs_repair 2>> $seqres.full
        _check_scratch_xfs_features NEEDSREPAIR > /dev/null && \
-               echo "Repair failed to clear NEEDSREPAIR on the $nr_writes writes test"
+               echo "Repair failed to clear NEEDSREPAIR on the $allowed_writes writes test"
 fi
 
 # success, all done