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>
This commit is contained in:
Filipe Manana
2019-11-19 12:07:34 +00:00
committed by Eryu Guan
parent 3414cae6d2
commit 67a76593ba
3 changed files with 215 additions and 0 deletions
+1
View File
@@ -203,3 +203,4 @@
198 auto quick volume
199 auto quick trim
200 auto quick send clone
201 auto quick punch log