mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
Filipe Manana
aaab9f3eb2
This test is motivated by a btrfs issue where a ranged fsync would
prevent a subsequent fsync from persisting any extents that were
dirty at the time of the first fsync but that were outside the range
of that first fsync (which should have been persisted by the second
fsync).
This bug in btrfs is fixed by the following linux kernel patch:
Btrfs: fix fsync data loss after a ranged fsync
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
20 lines
564 B
Plaintext
20 lines
564 B
Plaintext
QA output created by 325
|
|
wrote 65536/65536 bytes at offset 0
|
|
XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
File content before crash/reboot:
|
|
0000000 aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
|
|
*
|
|
0010000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
|
|
*
|
|
0170000 bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb
|
|
*
|
|
0200000
|
|
File content after crash/reboot and fs mount:
|
|
0000000 aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
|
|
*
|
|
0010000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
|
|
*
|
|
0170000 bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb
|
|
*
|
|
0200000
|