linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@libero.it>
To: Alexander Block <ablock84@googlemail.com>
Cc: 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 19:18:07 +0200	[thread overview]
Message-ID: <4FE205CF.9020509@libero.it> (raw)
In-Reply-To: <1340188512-5761-1-git-send-email-ablock84@googlemail.com>

Hi Alexander,

On 06/20/2012 12:35 PM, Alexander Block wrote:
> The patch also does proper vfs mount checks, so cross mount 
> point reflinks are not possible with this patch. It only allows cross 
> reflinks between two subvolumes which are in the same mount point.

Thanks for working on that. What happens if two subvolumes of the same
filesystem are mounted on two different places ?

I usually do:
 mount -o subvol=__active /dev/sdX /
 mount -o subvol=.        /dev/sdX /var/btrfs

So two different subvolumes of the same filesystem (the one on /dev/sdX)
are mounted on two different places.

Is it possible to do
 cp --reflink /tmp/foo /var/btrfs/tmp/foo2

Thanks
G.Baroncelli


  parent reply	other threads:[~2012-06-20 17:17 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 ` Goffredo Baroncelli [this message]
2012-06-20 17:27   ` [PATCH] Allow cross subvolume reflinks (2nd attempt) 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
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=4FE205CF.9020509@libero.it \
    --to=kreijack@libero.it \
    --cc=ablock84@googlemail.com \
    --cc=chris.mason@fusionio.com \
    --cc=dave@jikos.cz \
    --cc=hch@infradead.org \
    --cc=kreijack@inwind.it \
    --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).