linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Kai Herlemann <nesadaw@freenet.de>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: rollback to a snapshot and delete old top volume - missing of "@"
Date: Sat, 9 Jul 2016 08:30:30 +0300	[thread overview]
Message-ID: <57808BF6.6030204@gmail.com> (raw)
In-Reply-To: <CAJCQCtRMjGjcqPq08urpuRk-y4JvUO+LCuVqtsk1O5rxP68JEA@mail.gmail.com>

09.07.2016 00:50, Chris Murphy пишет:
>>
>> 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.
> 
> The only distro installer I know that works this way out of the box is
> Fedora/Red Hat's Anaconda. It leaves the default subvolume as 5, but
> does not install the OS there. Instead each mountpoint is created as a
> subvolume in that top level, and rootflags kernel parameter and fstab
> are used to assemble those subvolumes per the FHS virtually. It's
> completely discoverable, you can follow each step along the way, it's
> not obscured.
> 
> The additional benefit is no nested subvolumes.
> 

Does it use grub2? Where /boot/grub is located - on one of those
snapshots or on partition outside of btrfs control?

Does it support booting from previous read-only snapshot directly and/or
rollback to previous snapshot?

  parent reply	other threads:[~2016-07-09  5:30 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
2016-07-08 21:50         ` Chris Murphy
2016-07-08 23:21           ` Henk Slager
2016-07-09  5:30           ` Andrei Borzenkov [this message]
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=57808BF6.6030204@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --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).