From: Goffredo Baroncelli <kreijack@libero.it>
To: Mike Hommey <mh@glandium.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Can you please define "snapshot" and "subvolume"?
Date: Sat, 9 Oct 2010 15:55:01 +0200 [thread overview]
Message-ID: <201010091555.01645.kreijack@libero.it> (raw)
In-Reply-To: <20101009081537.GA4418@glandium.org>
On Saturday, 09 October, 2010, you (Mike Hommey) wrote:
> On Thu, Oct 07, 2010 at 11:13:18PM +0200, Goffredo Baroncelli wrote:
> > On Thursday, 07 October, 2010, David Nicol wrote:
> > > On Thu, Oct 7, 2010 at 8:18 AM, Mike Hommey <mh@glandium.org> wrote:
> > > > BTW, it would be very useful to be able to turn existing directories
> > > > into subvolumes.
> > >
> > > does a (link,unlink) move work across subvolumes?
> >
> > The link across subvolumes is not allowable. In the beginning it was
> > possible, but that was source of bugs. See the thread "Hard link across
> > subvolumes"
> >
> > http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg03286.html
>
> But couldn't cp --reflink be made to work?
>
I don't know why, but I can confirm that in the btrfs kernel source it is
checked the case that the "reflink" is preformed between two subvolume. And in
this case this action is denied.
http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-
unstable.git;a=blob;f=fs/btrfs/ioctl.c;h=9254b3d58dbef22974af3c7c61dbc9a4af7a33b6;hb=HEAD#l1489
--
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512
next prev parent reply other threads:[~2010-10-09 13:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 11:39 Can you please define "snapshot" and "subvolume"? Francis Galiegue
[not found] ` <AANLkTinGvkLSNq3xiOA5R777k54wbjfgDRKjXwJx0_fW@mail.gmail.com>
2010-10-07 12:00 ` Benjamin Griese
2010-10-07 12:30 ` Jérôme Poulin
2010-10-07 13:18 ` Mike Hommey
2010-10-07 14:00 ` Benjamin Griese
2010-10-07 20:52 ` David Nicol
2010-10-07 21:13 ` Goffredo Baroncelli
2010-10-07 21:14 ` Chester
2010-10-09 8:15 ` Mike Hommey
2010-10-09 13:55 ` Goffredo Baroncelli [this message]
2010-10-07 18:08 ` Goffredo Baroncelli
2010-10-07 20:48 ` David Nicol
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=201010091555.01645.kreijack@libero.it \
--to=kreijack@libero.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=mh@glandium.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 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.