From: Chris Mason <chris.mason@oracle.com>
To: "Jérôme Poulin" <jeromepoulin@gmail.com>
Cc: redneb <redneb@gmx.com>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: File cloning across subvolumes with BTRFS_IOC_CLONE ioctl
Date: Wed, 21 Jul 2010 11:32:24 -0400 [thread overview]
Message-ID: <20100721153224.GY3133@think> (raw)
In-Reply-To: <AANLkTil_bqyOwBIlkdZGyn1HAVKBMuEu4cem2UAhei3A@mail.gmail.com>
On Wed, Jul 21, 2010 at 11:11:13AM -0400, J=E9r=F4me Poulin wrote:
> I've got the same problem, and that post clearly seems to say it is p=
ossible.
> cp --reflink=3Dalways source subvolume1/ gives me:
> cp: failed to clone `xxxx': Invalid cross-device link
>=20
> Even on the same subvolume I get 10% of the files telling me the same=
=2E
>=20
> btrfs-bcp copy the files in its integrity.
Ok, this is a bug in the ioctl. I'll fix it up.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-07-21 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 5:39 File cloning across subvolumes with BTRFS_IOC_CLONE ioctl redneb
2010-07-21 15:11 ` Jérôme Poulin
2010-07-21 15:32 ` Chris Mason [this message]
2010-07-26 12:55 ` Jérôme Poulin
2010-07-26 13:00 ` Jérôme Poulin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100721153224.GY3133@think \
--to=chris.mason@oracle.com \
--cc=jeromepoulin@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=redneb@gmx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.