From: Hubert Kario <hka@qbs.com.pl>
To: "Jérôme Poulin" <jeromepoulin@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Norbert Scheibner <scno@gmx.net>
Subject: Re: cross-subvolume cp --reflink
Date: Sun, 29 Apr 2012 01:53:54 +0200 [thread overview]
Message-ID: <2272893.XFoXOC5Zif@bursa22> (raw)
In-Reply-To: <CALJXSJpjOX3t6Xa=gFF2p13eSb+SJfRc_pc0d5ScShnK-5BwkQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
On Sunday 01 of April 2012 11:42:23 Jérôme Poulin wrote:
> On Sun, Apr 1, 2012 at 11:27 AM, Norbert Scheibner <scno@gmx.net> wrote:
> > Some users tested this patch successfully for week,s or months in 2 or 3
> > kernel versions since then, true?
> If this feature must be implented in VFS in another patch, why not
> just activate what works and make the future patch disable it again?
Why would (should) it be impleemented in VFS? reflink copy is completely
different from normal copy and hard link.
Subvolumes in btrfs are barriers *only* in btrfs and not visible in VFS.
IMHO it's strictly btrfs business and not supporting reflink copy between
arbitrary directories is a bug.
Regards,
--
Hubert Kario
QBS - Quality Business Software
02-656 Warszawa, ul. Ksawerów 30/85
tel. +48 (22) 646-61-51, 646-74-24
www.qbs.com.pl
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2346 bytes --]
next prev parent reply other threads:[~2012-04-28 23:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 15:27 cross-subvolume cp --reflink Norbert Scheibner
2012-04-01 15:30 ` Konstantinos Skarlatos
2012-04-01 16:41 ` Norbert Scheibner
2012-04-01 16:45 ` Konstantinos Skarlatos
2012-04-01 17:07 ` Norbert Scheibner
2012-04-01 17:19 ` Konstantinos Skarlatos
2012-04-01 18:11 ` Norbert Scheibner
2012-04-01 19:42 ` Konstantinos Skarlatos
[not found] ` <4F788EE2.4010105@univie.ac.at>
2012-04-01 18:39 ` Norbert Scheibner
2012-04-01 19:27 ` Konstantinos Skarlatos
2012-04-02 8:29 ` David Sterba
2012-04-01 15:42 ` Jérôme Poulin
2012-04-28 23:53 ` Hubert Kario [this message]
2012-04-29 20:05 ` Norbert Scheibner
2012-08-17 4:20 ` james northrup
2012-08-17 5:20 ` Marc MERLIN
2012-08-19 5:08 ` Mitch Harder
2012-08-19 6:43 ` Marc MERLIN
[not found] ` <CAPkEcwgSZ8umbFeuZ-fQAFAprBubL58eFSf4TQ=Z13ks8i9DOQ@mail.gmail.com>
2012-08-20 18:08 ` Jérôme Poulin
2012-08-21 0:20 ` james northrup
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=2272893.XFoXOC5Zif@bursa22 \
--to=hka@qbs.com.pl \
--cc=jeromepoulin@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=scno@gmx.net \
/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.