btrfs: test for send with compressed file extents
authorFilipe Manana <fdmanana@suse.com>
Thu, 14 May 2015 10:27:53 +0000 (20:27 +1000)
committerDave Chinner <david@fromorbit.com>
Thu, 14 May 2015 10:27:53 +0000 (20:27 +1000)
commit917efe2a18849568d7b42160f0c919819d45deda
tree325f9d1e10fc155fe22b2b46ff5d501e913d34fd
parent2ba510dc7500114313941634f029c34baf504abf
btrfs: test for send with compressed file extents

Test that an incremental send issues valid clone operations for
compressed file extents.

For some compressed extents, namely those referred by a file extent item
with a non-zero data offset, btrfs could issue a clone operation in the
send stream with an offset and length pair that were not entirely
contained in the source file's range, causing the receiving side to get
-EINVAL errors from the clone ioctl when attempting to perform the clone
operations.

This issue was fixed by the following linux kernel btrfs patch:

  Btrfs: incremental send, fix clone operations for compressed extents

Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: David Sterba <dsterba@suse.cz>
Signed-off-by: Dave Chinner <david@fromorbit.com>
tests/btrfs/094 [new file with mode: 0755]
tests/btrfs/094.out [new file with mode: 0644]
tests/btrfs/group