From: Goffredo Baroncelli <kreijack@inwind.it>
To: Chris Murphy <lists@colorremedies.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Question about btrfs as root filesystem
Date: Fri, 08 Nov 2013 18:59:25 +0100 [thread overview]
Message-ID: <527D267D.9010403@inwind.it> (raw)
In-Reply-To: <8B95F9DF-83EC-4F49-8E5E-B5052FB778F9@colorremedies.com>
On 2013-11-08 18:44, Chris Murphy wrote:
>
> On Nov 8, 2013, at 5:55 AM, Goffredo Baroncelli <kreijack@libero.it>
> <kreijack@libero.it> wrote:
>>
>> Instead of using set-default, I am used to rename the subvolume.
>> I.E. I assume that the root filesystem is a subvolume always called
>> "__active". When I want to rollback, I rename "__active" in
>> "__broken" (or remove it), then I rename (or re-snapshot)
>> "snapshot-yyyymmdd" in "__active".
>>
>>>> That way, we ensure the best compatibility and lowest
>>>> maintenance,
>>> as we don't overwrite default init functions.
>>>
>>> I'm sympathetic to the alternative problem, which is that you
>>> need to alter grub.cfg to use the proper rootflags=subvol= to
>>> explicitly use the proper snapshot, and also it would mean
>>> altering the /etc/fstab within that snapshot.
>>
>> With rename you can address both the issues
>
> Now I don't know what snapshot that is, since it's just renamed to
> some non-descriptive name like "root" which happens to, by
> convention, always be the active root. This is the problem with using
> user domain to store contextual metadata. We need another way to do
> this, rather than inject these changes into filename/foldername which
> are primarily user domain. And we need agreement on a right way to do
> this rather than distribution convention.
Put all the required information in an xattr...
>
> We need some distribution collaboration in this area, or this is
> going to turn into an end-user pain point, with multiboot users top
> on the list of the injured.
I fully agree: whatever solution we found, it has to be shared across
all distributions.
>
>
> Chris Murphy-- To unsubscribe from this list: send the line
> "unsubscribe linux-btrfs" in the body of a message to
> majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html
>
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2013-11-08 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 23:45 Question about btrfs as root filesystem Michael Göhler
2013-11-08 1:33 ` Chris Murphy
2013-11-08 13:41 ` Michael Göhler
2013-11-08 19:30 ` Chris Murphy
2013-11-08 9:39 ` Duncan
2013-11-08 12:55 ` R: " Goffredo Baroncelli <kreijack@libero.it>
2013-11-08 17:44 ` Chris Murphy
2013-11-08 17:59 ` Goffredo Baroncelli [this message]
2013-11-08 19:43 ` 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=527D267D.9010403@inwind.it \
--to=kreijack@inwind.it \
--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 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).