From: Lennart Poettering <lennart@poettering.net>
To: Chris Mason <clm@fb.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Recursive subvolume snapshots and deletion?
Date: Wed, 25 Mar 2015 12:21:47 +0100 [thread overview]
Message-ID: <20150325112147.GB21533@gardel-login> (raw)
In-Reply-To: <1427114207.5707.2@mail.thefacebook.com>
On Mon, 23.03.15 08:36, Chris Mason (clm@fb.com) wrote:
> On Mon, Mar 23, 2015 at 12:57 AM, Lennart Poettering <mzerqung@0pointer.de>
> wrote:
> >Heya!
> >
> >So what's the story on recursive btrfs snapshotting and snapshot
> >removal? Since a while systemd has now by default creating btrfs
> >subvolumes for /var/lib/machines for example. Now, if that code is run
> >inside a container, and the container itself already is stored in a
> >subvolume we end up with a subvolume inside a subvolume, which
> >currently breaks snapshotting and deletion of the outer container
> >subvolume.
> >
> >What's the plan regarding recursive versions of the operations? Any
> >plan to add this? We could work around this in userspace, of course,
> >but it would not be atomic, and I'd much prefer if the kernel could do
> >this on its own!
>
> Hi Lennart,
>
> I've got a patch to btrfs-progs that can do the recursive snapshotting, let
> me clean it up and submit to Dave. For recursive deletion I think the same
> method can be used.
OK, so this means you want this to be solved in userspace, hence in a
non-atomic fashion?
What precisely will your code do? Enumerate the subvolumes and simply
snapshot all subvolumes below the desired path? Or anything smarter?
Lennart
--
Lennart Poettering, Red Hat
prev parent reply other threads:[~2015-03-25 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 4:57 Recursive subvolume snapshots and deletion? Lennart Poettering
2015-03-23 12:36 ` Chris Mason
2015-03-25 11:21 ` Lennart Poettering [this message]
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=20150325112147.GB21533@gardel-login \
--to=lennart@poettering.net \
--cc=clm@fb.com \
--cc=linux-btrfs@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