From: Marc MERLIN <marc@merlins.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Planning for subvolumes of subvolumes and btrfs send/receive
Date: Sun, 20 Apr 2014 22:48:29 -0700 [thread overview]
Message-ID: <20140421054829.GT7884@merlins.org> (raw)
In-Reply-To: <5B1404BF-F985-4201-87FD-CBB3E6776531@colorremedies.com>
On Sun, Apr 20, 2014 at 11:39:22PM -0600, Chris Murphy wrote:
>
> On Apr 20, 2014, at 1:46 PM, Marc MERLIN <marc@merlins.org> wrote:
>
> > Can you help me design this right?
> >
> > Long story short, I'm wondering if I can use btrfs send to copy sub
> > subvolumes (by snapshotting a parent subvolume, and hopefully getting
> > all the children underneath). My reading so far, says no.
>
> That's my understanding thus far also. Seems like first a recursive read-only snapshot creation is a pre-requisite, since a read-only snapshot is needed first in order to send it.
>
> I think the seed device method is a better way to do this, though I'm not sure what state its in.
Thank you both for the confirmation.
This indeed makes it too much of a pain for me, so I think I will go
back to making hardlinks like I did with ext4
That way I won't need subvolumes of subvolumes and will be able to do
snapshots and replication more easily.
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2014-04-21 5:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 19:46 Planning for subvolumes of subvolumes and btrfs send/receive Marc MERLIN
2014-04-21 5:21 ` Duncan
2014-04-21 5:39 ` Chris Murphy
2014-04-21 5:48 ` Marc MERLIN [this message]
2014-04-21 6:08 ` Chris Murphy
2014-04-21 21:51 ` 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=20140421054829.GT7884@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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.