From: Lennart Poettering <mzerqung@0pointer.de>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Recursive subvolume snapshots and deletion?
Date: Mon, 23 Mar 2015 05:57:18 +0100 [thread overview]
Message-ID: <20150323045718.GE19498@gardel-login> (raw)
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!
Lennart
next reply other threads:[~2015-03-23 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 4:57 Lennart Poettering [this message]
2015-03-23 12:36 ` Recursive subvolume snapshots and deletion? Chris Mason
2015-03-25 11:21 ` Lennart Poettering
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=20150323045718.GE19498@gardel-login \
--to=mzerqung@0pointer.de \
--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