xfs/{319,323}: don't checksum files after log recovery
authorDarrick J. Wong <darrick.wong@oracle.com>
Wed, 30 Aug 2017 04:40:50 +0000 (21:40 -0700)
committerEryu Guan <eguan@redhat.com>
Sun, 3 Sep 2017 04:19:26 +0000 (12:19 +0800)
commitfc3c28b307847a60ba9c463dc47a61c64c07debf
tree0ac561eb88ef2c8cece7319fab1e0a4d66a53c4b
parentfb3c560d49a8f33b771e44db3978f0c7ab53ef3e
xfs/{319,323}: don't checksum files after log recovery

These two tests simulate log failure during a reflink operation.
However, the contents of the target of the reflink operation depend
on the block size, so we cannot hardcode md5 hashes in this test.
Since the whole point of the test is to ensure that the the complex
chain of transactions actually finishes no matter where the
interruption, it is sufficient simply to run the usual end-of-test
fsck to look for corrupt metadata.

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>
tests/xfs/319
tests/xfs/319.out
tests/xfs/323
tests/xfs/323.out