mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
Darrick J. Wong
c4288aec3c
When we're using dm-error to simulate failed devices, we don't really know if the write or the fdatasync is going to receive the EIO. For tests that make a single (failed) write attempt and never retry, it's sufficient to check that the file md5 doesn't change after recovery. For tests that /do/ retry the write, we should capture the entire output and just look for the word error instead of enshrining the exact perror message (filename/function call and everything) in the golden output. 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>
11 lines
312 B
Plaintext
11 lines
312 B
Plaintext
QA output created by 265
|
|
Format and mount
|
|
Create the original files
|
|
Compare files
|
|
1886e67cf8783e89ce6ddc5bb09a3944 SCRATCH_MNT/test-265/file1
|
|
1886e67cf8783e89ce6ddc5bb09a3944 SCRATCH_MNT/test-265/file2
|
|
CoW and unmount
|
|
Compare files
|
|
1886e67cf8783e89ce6ddc5bb09a3944 SCRATCH_MNT/test-265/file1
|
|
Check for damage
|