From: Chris Murphy <lists@colorremedies.com>
To: Kai Herlemann <nesadaw@freenet.de>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: rollback to a snapshot and delete old top volume - missing of "@"
Date: Fri, 8 Jul 2016 15:39:23 -0600 [thread overview]
Message-ID: <CAJCQCtSd9NTffBJUFwT2ja6PahdCqa=Sm5joP3aptD4OmVoW7w@mail.gmail.com> (raw)
In-Reply-To: <0e0dcbb3-73a4-0c5f-9978-67109d505b79@freenet.de>
On Fri, Jul 8, 2016 at 2:08 PM, Kai Herlemann <nesadaw@freenet.de> wrote:
> If here any developers read along: I'd like to suggest that there's
> automatically made a subvolume "@" by default, which is set as default
> subvolume, or a tip to the distribution, that it would made sense to do that
> with the installation. It would protect other users against confusion and
> work like I had it.
I think that upstream won't do that or recommend it. There is already
a subvolume created at mkfs time, that's subvolid=5 (a.k.a. 0) and it
is set as the default subvolume. I don't see the point in having two
of them. If you want it, make it. If your distro wants it, it should
be done in the installer, not mkfs.
Further I think it's inappropriate to take 'btrfs sub set-default'
away from the user. That is a user owned setting. It is not OK for
some utility to assert domain over that setting, and depend on it for
proper booting. It makes the entire boot process undiscoverable,
breaks self-describing boot process which are simpler to understand
and troubleshoot, in favor of secret decoder ring booting that now
requires even more esoteric knowledge on the part of users. So I think
it's a bad design.
Instead those utilities should employ rootflags=subvol or subvolid to
explicitly use a particular fs tree for rootfs, rather that hide this
fact by using subvolume set-default.
--
Chris Murphy
next prev parent reply other threads:[~2016-07-08 21:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 12:17 rollback to a snapshot and delete old top volume - missing of "@" Kai Herlemann
2016-07-07 16:01 ` Henk Slager
2016-07-07 17:40 ` Chris Murphy
2016-07-07 18:27 ` Henk Slager
2016-07-08 20:08 ` Kai Herlemann
2016-07-08 21:39 ` Chris Murphy [this message]
2016-07-08 21:50 ` Chris Murphy
2016-07-08 23:21 ` Henk Slager
2016-07-09 5:30 ` Andrei Borzenkov
2016-07-09 12:45 ` Chris Murphy
2016-07-09 1:20 ` Chris Murphy
2016-07-08 18:51 ` Andrei Borzenkov
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='CAJCQCtSd9NTffBJUFwT2ja6PahdCqa=Sm5joP3aptD4OmVoW7w@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nesadaw@freenet.de \
/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;
as well as URLs for NNTP newsgroup(s).