Have a look at line 998, ioctl.c, inside btrfs_ioctl_clone(),
the src->i_size(the size of the testfile created by touch) is just 0, and this
will cause btrfs_ioctl_clone just return -EINVAL.
I'm not sure if it makes sense to clone a file which actually doesn't have any
data extents.
On Wednesday
Josef Bacik wrote:
>On Sun, Dec 13, 2009 at 12:29:03AM +, Jason White wrote:
>> I am testing a Btrfs root file system with Debian (kernel 2.6.32) under KVM.
>>
>> ja...@vrtl:~$ touch testfile
>> ja...@vrtl:~$ cp --reflink testfile /tmp
>> cp: failed to clone `/tmp/testfile': Invalid argument
how about supporting the operation, as a feature, and allowing a file
to be in two different subvolumes at the same time? Would that make
the link semantics too confusing?
--
Is it the time when there isn't time to discuss but there is time to act yet?
--
To unsubscribe from this list: send the l
It looks like the git trees at:
http://git.kernel.org/smart/pub/scm/linux/kernel/git/mason/btrfs-progs-unstable.git
and
http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-unstable.git;a=summary
are several weeks out of date. For example, the patch here:
http://news.gmane.org/gmane.comp.fil
