All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lennart Poettering <mzerqung@0pointer.de>
To: Chris Murphy <lists@colorremedies.com>
Cc: kreijack@inwind.it,
	systemd Mailing List <systemd-devel@lists.freedesktop.org>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [systemd-devel] systemd and nested Btrfs subvolumes
Date: Mon, 23 Mar 2015 05:53:14 +0100	[thread overview]
Message-ID: <20150323045314.GD19498@gardel-login> (raw)
In-Reply-To: <CAJCQCtRFnCm=ug4Byd=A+mT+CrUPrrGW_T+SzYaD+mLc6wypOA@mail.gmail.com>

On Fri, 20.03.15 18:08, Chris Murphy (lists@colorremedies.com) wrote:

> Sure but now it's missing if you do a rollback, or if you mount any
> different root tree, so immediately special handling is needed.
> 
> If machines is a subvolume at the top level, it can always be mounted
> at /var/lib/machines regardless of which root is used.
> 
> I also think this is more consistent with
> http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html
> specifically the section "What We Propose" when it comes to the
> location and naming convention for Btrfs subvolumes.

containers are recursively stackable, hence having toplevel subvolumes
doesn't work, since the containers should be able to have
subcontainers of their own...

Also, it kinda defeats the whole point of btrfs' subvolume concept,
where subvolumes are little more than special directories.

Lennart

-- 
Lennart Poettering, Red Hat

  reply	other threads:[~2015-03-23  5:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJCQCtRFUMAeyjLxADKLVaHA0wqQBY_tbyZoJJ6Hze7AeeTa_w@mail.gmail.com>
2015-03-20 19:22 ` [systemd-devel] systemd and nested Btrfs subvolumes Goffredo Baroncelli
2015-03-20 19:34 ` Goffredo Baroncelli
2015-03-21  0:08   ` Chris Murphy
2015-03-23  4:53     ` Lennart Poettering [this message]
2015-03-23  5:27       ` Chris Murphy

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=20150323045314.GD19498@gardel-login \
    --to=mzerqung@0pointer.de \
    --cc=kreijack@inwind.it \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=systemd-devel@lists.freedesktop.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.