Files
apfstests/tests/btrfs/201.out
T
Filipe Manana 67a76593ba btrfs: test fsync after hole punching when using the no-holes feature
Test that when we have the no-holes feature enabled and a specific
metadata layout, if we punch a hole that starts at file offset 0 and
fsync the file, after replaying the log the hole exists.

This currently fails on btrfs but is fixed by a patch for the linux
kernel with the following subject:

 "Btrfs: fix missing hole after hole punching and fsync when using NO_HOLES"

Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
2019-11-25 00:16:29 +08:00

25 lines
960 B
Plaintext

QA output created by 201
Testing with hole offset 0 hole length 65536
File digest before power failure:
e1e40ea5ab31cc36fb74830a6293eb2b SCRATCH_MNT/bar
File digest after power failure and log replay:
e1e40ea5ab31cc36fb74830a6293eb2b SCRATCH_MNT/bar
Testing with hole offset 786432 hole length 54919168
File digest before power failure:
8bfa78372c90f7418ce6a90ba3a92b7f SCRATCH_MNT/bar
File digest after power failure and log replay:
8bfa78372c90f7418ce6a90ba3a92b7f SCRATCH_MNT/bar
Testing with hole offset 720896 hole length 54919168
File digest before power failure:
327a10e71854c55a0439b859665a4fdd SCRATCH_MNT/bar
File digest after power failure and log replay:
327a10e71854c55a0439b859665a4fdd SCRATCH_MNT/bar
Testing with hole offset 655360 hole length 54919168
File digest before power failure:
2b060d70788a69e081013f0ce0e52921 SCRATCH_MNT/bar
File digest after power failure and log replay:
2b060d70788a69e081013f0ce0e52921 SCRATCH_MNT/bar