From: Hubert Kario <hka@qbs.com.pl>
To: linux-btrfs@vger.kernel.org
Subject: Cross-subvolume reflink copy (BTRFS_IOC_CLONE over subvolume boundaries)
Date: Tue, 14 Feb 2012 00:52:33 +0100 [thread overview]
Message-ID: <2704295.VfXjvSRAYV@bursa01> (raw)
It's been nearly a year since the patches needed to implement a reflink=
ed copy=20
between subvolumes have been posted=20
(http://permalink.gmane.org/gmane.comp.file-systems.btrfs/9865 ) and I =
still=20
get "Invalid cross-device link" error with Linux 3.2.4 while I try to d=
o a cp=20
--reflink between subvolumes.
This is a *very* useful feature to have (think offline file-level dedup=
lication=20
for one thing).
=46rom what I was able to find in the archives, the only objection (use=
rland=20
operation crossing subvolume boundaries) was rebutted by Chris Mason.=20
Is there something else that I missed?
Regards,
--=20
Hubert Kario
QBS - Quality Business Software
02-656 Warszawa, ul. Ksawer=F3w 30/85
tel. +48 (22) 646-61-51, 646-74-24
www.qbs.com.pl
--
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 reply other threads:[~2012-02-13 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 23:52 Hubert Kario [this message]
2012-02-14 2:47 ` Cross-subvolume reflink copy (BTRFS_IOC_CLONE over subvolume boundaries) 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=2704295.VfXjvSRAYV@bursa01 \
--to=hka@qbs.com.pl \
--cc=linux-btrfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox