Files
apfstests/tests/btrfs/098.out
T
Filipe Manana 83288d506e btrfs: fsync after extent cloning
Test that if we fsync a file that got one extent partially cloned into a
lower file offset, after a power failure our file has the same content it
had before the power failure and after the extent cloning operation.

This test is motivated by an issue found in btrfs that is fixed by the
linux kernel patch titled:

  "Btrfs: fix file read corruption after extent cloning and fsync"

Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Eryu Guan <eguan@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
2015-09-21 13:06:17 +10:00

8 lines
291 B
Plaintext

QA output created by 098
wrote 102400/102400 bytes at offset 819200
XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
File digest before power failure:
39b386375971248740ed8651d5a2ed9f SCRATCH_MNT/foo
File digest after log replay:
39b386375971248740ed8651d5a2ed9f SCRATCH_MNT/foo