This gives EXDEV for clone operations that btrfs could otherwise execute
and with slight change of circumstances will actually execute fine.
Imagine we have a btrfs on /dev/mapper/foobar with subvols /foo and
/bar. Let’s also imagine top of said fs in mounted at /mnt. In this
case, a cross-subvol clone of /mnt/foo/srcfile to /mnt/bar/dstfile will
succeed.
However, if only the individual subvols were mounted like this:
/dev/mapper/foobar on /mnt (subvol=foo)
/dev/mapper/foobar on /mnt2 (subvol=bar),
then a clone of /mnt/srcfile to /mnt2/dstfile will fail with EXDEV even
though it is otherwise equal to the former clone operation.
Would anyone care to shed some light on this? Is it due to legacy
policy? Am I missing something?
Thanks
–Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
