diff options
author | Filipe Manana <fdmanana@gmail.com> | 2014-05-25 04:49:24 +0100 |
---|---|---|
committer | Chris Mason <clm@fb.com> | 2014-06-09 17:20:59 -0700 |
commit | 1af56070e3ef9477dbc7eba3b9ad7446979c7974 (patch) | |
tree | d6685f9c0cbff57135a11fe573fbb2e0779a5d16 /fs/cachefiles | |
parent | a79b7d4b3e8118f265dcb4bdf9a572c392f02708 (diff) | |
download | linux-1af56070e3ef9477dbc7eba3b9ad7446979c7974.tar.bz2 |
Btrfs: send, don't error in the presence of subvols/snapshots
If we are doing an incremental send and the base snapshot has a
directory with name X that doesn't exist anymore in the second
snapshot and a new subvolume/snapshot exists in the second snapshot
that has the same name as the directory (name X), the incremental
send would fail with -ENOENT error. This is because it attempts
to lookup for an inode with a number matching the objectid of a
root, which doesn't exist.
Steps to reproduce:
mkfs.btrfs -f /dev/sdd
mount /dev/sdd /mnt
mkdir /mnt/testdir
btrfs subvolume snapshot -r /mnt /mnt/mysnap1
rmdir /mnt/testdir
btrfs subvolume create /mnt/testdir
btrfs subvolume snapshot -r /mnt /mnt/mysnap2
btrfs send -p /mnt/mysnap1 /mnt/mysnap2 -f /tmp/send.data
A test case for xfstests follows.
Reported-by: Robert White <rwhite@pobox.com>
Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com>
Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'fs/cachefiles')
0 files changed, 0 insertions, 0 deletions