mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
fc3c28b307
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>
15 lines
409 B
Plaintext
15 lines
409 B
Plaintext
QA output created by 323
|
|
Format filesystem
|
|
Create files
|
|
Check files
|
|
2a4f043bf9730a9e8882c9264b9797b3 SCRATCH_MNT/file1
|
|
4155b81ac6d45c0182fa2bc03960f230 SCRATCH_MNT/file3
|
|
Inject error
|
|
Try to reflink
|
|
XFS_IOC_CLONE_RANGE: Input/output error
|
|
FS should be shut down, touch will fail
|
|
touch: cannot touch 'SCRATCH_MNT/badfs': Input/output error
|
|
Remount to replay log
|
|
FS should be online, touch should succeed
|
|
Done
|