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 16 December 2009 07:37:42 Jason White wrote:
> Josef Bacik <josef@xxxxxxxxxx> wrote:
> >On Sun, Dec 13, 2009 at 12:29:03AM +0000, Jason White wrote:
> >> I am testing a Btrfs root file system with Debian (kernel 2.6.32) under
> >> KVM.
> >>
> >> jason@vrtl:~$ touch testfile
> >> jason@vrtl:~$ cp --reflink testfile /tmp
> >> cp: failed to clone `/tmp/testfile': Invalid argument
> >>
> >> This is with GNU Coreutils 8.0 taken from debian Sid.
> >>
> >> Is this a Coreutils issue, a Btrfs problem or something in my local
> >> configuration?
> >
> >Try using bcp, if that works then its likely a problem with coreutils.
>
> After reporting this to Debian and engaging on follow-up discussion, it
> turns out that bcp copies the data if the ioctl() call to clone the file
> fails, as can be seen from the Python code (which I should have read, but
> didn't...).
>
> Unfortunately the ioctl() call is failing both in bcp and in cp --reflink.
>
> Here's partial strace output from the latter.
>
> cp --reflink testfile testfile2
>
> open("testfile", O_RDONLY) = 3
> fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
> open("testfile2", O_WRONLY|O_CREAT|O_EXCL, 0644) = 4
> fstat(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
> ioctl(4, 0x40049409, 0x3) = -1 EINVAL (Invalid argument)
>
> Kernel 2.6.32 (debian Sid), x86-64 architecture.
>
> Suggestions welcome.
>
> Debian bug report:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561225
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
