xfs/130,235: deal with an unreplayable dirty log

Now that we have log replay items, an FS shutdown due to a corrupt
btree results in a log that can't be replayed.  The only solution
here is to zap the log when we're fixing the corrupt fs, so do that
here.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Eryu Guan <eguan@redhat.com>
Signed-off-by: Eryu Guan <eguan@redhat.com>
This commit is contained in:
Darrick J. Wong
2016-08-25 16:28:38 -07:00
committed by Eryu Guan
parent 5bcb0b7d8c
commit acede2049a
2 changed files with 4 additions and 2 deletions
+2 -1
View File
@@ -87,7 +87,8 @@ _cp_reflink "${SCRATCH_MNT}/file1" "${SCRATCH_MNT}/file4" 2> /dev/null && \
umount "${SCRATCH_MNT}"
echo "+ repair fs"
_scratch_xfs_repair >> "$seqres.full" 2>&1
_disable_dmesg_check
_repair_scratch_fs >> "$seqres.full" 2>&1
_scratch_xfs_repair >> "$seqres.full" 2>&1
echo "+ mount image (2)"
+2 -1
View File
@@ -85,7 +85,8 @@ test -s ${SCRATCH_MNT}/file4 && _fail "should not be able to copy with busted rm
umount ${SCRATCH_MNT}
echo "+ repair fs"
_scratch_xfs_repair >> $seqres.full 2>&1
_disable_dmesg_check
_repair_scratch_fs >> "$seqres.full" 2>&1
_scratch_xfs_repair >> $seqres.full 2>&1
echo "+ mount image (2)"