btrfs: test fsync after hole punching when using the no-holes feature
authorFilipe Manana <fdmanana@suse.com>
Tue, 19 Nov 2019 12:07:34 +0000 (12:07 +0000)
committerEryu Guan <guaneryu@gmail.com>
Sun, 24 Nov 2019 16:16:29 +0000 (00:16 +0800)
commit67a76593ba2e33eabeb38c9fa43864da906c3ec7
tree0b5737bfda405ac4bc612658b455bc9d8ed06ded
parent3414cae6d231e69a08e244da242cdcaf59aeac9f
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>
tests/btrfs/201 [new file with mode: 0755]
tests/btrfs/201.out [new file with mode: 0644]
tests/btrfs/group