Files
apfstests/tests/btrfs/105.out
T
Filipe Manana 88b71e7bff btrfs: incremental send after replacing a file
Test that an incremental send works after a file from the parent snapshot
gets replaced in the send snapshot by another one at the same exact
location, with the same name and with the same inode number.

This test used to fail after the linux kernel commit 8b191a684968
("Btrfs: incremental send, check if orphanized dir inode needs delayed
rename") and it's fixed by patch titled:

  "Btrfs: send, fix corner case for reference overwrite detection"

Signed-off-by: Martin Raiber <martin@urbackup.org>
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Eryu Guan <eguan@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
2015-10-14 14:07:42 +11:00

12 lines
538 B
Plaintext

QA output created by 105
wrote 65536/65536 bytes at offset 0
XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
File digest before being replaced:
9802287a6faa01a1fd0e01732b732fca SCRATCH_MNT/mysnap1/foo/bar
wrote 98304/98304 bytes at offset 0
XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
File digest in the original filesystem after being replaced:
de277dfac706c359613033120349cf88 SCRATCH_MNT/mysnap2_ro/foo/bar
File digest in the new filesystem:
de277dfac706c359613033120349cf88 SCRATCH_MNT/mysnap2_ro/foo/bar