All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Cc: sensille@gmx.net, larry@elder-gods.org, hch@infradead.org
Subject: Re: [PATCH 0/2] btrfs: allow cross-subvolume BTRFS_IOC_CLONE
Date: Thu, 31 Mar 2011 13:12:14 +0200	[thread overview]
Message-ID: <4D94618E.3030300@wpkg.org> (raw)

Arne Jansen wrote:

>> On Thu, Mar 31, 2011 at 12:00:11AM -0400, Larry D'Anna wrote:
>>> This is a simple patch to allow reflinks to be made crossing subvolume
>>> boundaries.
>>
>> NAK.  subvolumes will have to become vfsmounts sooner or later, and we
>> really must not support any operations spanning mountpoints.
>
> In what way would this interfere? the reflinked file gets its own inum
> in its own mountpoint. The two files only internally share some disk
> space.

Similarly, it would be pity if proposed deduplication couldn't cross 
subvolume boundaries...


-- 
Tomasz Chmielewski
http://wpkg.org


             reply	other threads:[~2011-03-31 11:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 11:12 Tomasz Chmielewski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-31  4:00 [PATCH 0/2] btrfs: allow cross-subvolume BTRFS_IOC_CLONE Larry D'Anna
2011-03-31  6:36 ` Christoph Hellwig
2011-03-31  6:44   ` Arne Jansen
2011-03-31 12:02   ` Chris Mason
2011-04-01 13:34     ` Christoph Hellwig
2011-04-01 13:40       ` Chris Mason
2011-04-02  1:59         ` Fajar A. Nugraha
2011-12-22 12:24         ` Chris Samuel
2012-01-06 12:04           ` Konstantinos Skarlatos
2012-01-06 17:57             ` David Sterba
2012-01-09  6:58               ` Marios Titas
2012-01-09 13:31                 ` Jérôme Poulin
2012-01-19 16:52                   ` Jérôme Poulin
2011-04-02 15:51       ` Ken Drummond
2011-04-02 16:56         ` Larry D'Anna
2011-04-02 20:01           ` 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=4D94618E.3030300@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=hch@infradead.org \
    --cc=larry@elder-gods.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sensille@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.