btrfs: send with no-holes enabled, fallocate and hole punching

Test that an incremental send with not corrupt data when the source
filesystem has the no-holes feature enabled, a file has prealloc
(unwritten) extents that start after its size and hole is punched (after
the first snapshot is made) that removes all extents from some offset up
to the file's size.

This currently fails on any kernel version starting from 3.16, and it's
by a patch titled:

 "Btrfs: incremental send, fix file corruption when no-holes feature is enabled"

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-05-20 09:55:47 +01:00
committed by Eryu Guan
parent 9f2e4554c5
commit c37f9a66df
3 changed files with 98 additions and 0 deletions
+1
View File
@@ -190,3 +190,4 @@
185 volume
186 auto quick send volume
187 auto send dedupe clone balance
188 auto quick send prealloc punch