btrfs: incremental send after replacing a top level inode

Test that an incremental send operation does not fail when a new
inode replaces an old inode that has the same number but different
generation, and both are direct children of the subvolume/snapshot
root.

This is fixed by the following patch for the linux kernel:

  "Btrfs: send, fix failure to rename top level inode due to name
   collision"

Signed-off-by: Robbie Ko <robbieko@synology.com>
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Eryu Guan <eguan@redhat.com>
Signed-off-by: Eryu Guan <eguan@redhat.com>
This commit is contained in:
Filipe Manana
2017-01-12 03:13:13 +00:00
committed by Eryu Guan
parent 9b80c46ed0
commit 6fc65f42eb
3 changed files with 136 additions and 0 deletions
+1
View File
@@ -134,3 +134,4 @@
130 auto clone send
131 auto quick
132 auto enospc
133 auto quick send