From: Goffredo Baroncelli <kreijack@inwind.it>
To: Alexander Block <ablock84@googlemail.com>
Cc: Calvin Walton <calvin.walton@kepstin.ca>,
linux-btrfs@vger.kernel.org, dave@jikos.cz, hch@infradead.org,
linux-fsdevel@vger.kernel.org, chris.mason@fusionio.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Allow cross subvolume reflinks (2nd attempt)
Date: Wed, 20 Jun 2012 22:15:32 +0200 [thread overview]
Message-ID: <4FE22F64.3010101@inwind.it> (raw)
In-Reply-To: <CAB9VWqAF5QS6BppN7Xei6JGsDU9ThBpcipk4r=PCwzu8c2AKgQ@mail.gmail.com>
On 06/20/2012 10:05 PM, Alexander Block wrote:
> On Wed, Jun 20, 2012 at 8:11 PM, Goffredo Baroncelli <kreijack@libero.it> wrote:
>>
>> Yes please, could someone explain the reason behind this decision ? May
>> be there are valid reasons, I am asking only to know which ones ?
>>
> The reason is that at the moment no user visible operations span mount
> boundaries
> and there were discussion on whether this should be allowed for the
> clone ioctl or
> not.
Yes, I understood the same. But nobody was able to explain why .
For the moment, I would already be happy to have cross subvolume reflinks
> which do not span mount points, this would already be much more as we have at
> the moment.
This is reasonable.
> .
>
next prev parent reply other threads:[~2012-06-20 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 10:35 [PATCH] Allow cross subvolume reflinks (2nd attempt) Alexander Block
2012-06-20 10:35 ` [PATCH] btrfs: allow cross-subvolume file clone Alexander Block
2012-06-20 17:18 ` [PATCH] Allow cross subvolume reflinks (2nd attempt) Goffredo Baroncelli
2012-06-20 17:27 ` Alexander Block
2012-06-20 18:07 ` Calvin Walton
2012-06-20 18:11 ` Goffredo Baroncelli
2012-06-20 20:05 ` Alexander Block
2012-06-20 20:15 ` Goffredo Baroncelli [this message]
2012-06-27 17:21 ` Marc MERLIN
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=4FE22F64.3010101@inwind.it \
--to=kreijack@inwind.it \
--cc=ablock84@googlemail.com \
--cc=calvin.walton@kepstin.ca \
--cc=chris.mason@fusionio.com \
--cc=dave@jikos.cz \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).