From: Phillip Susi <phill@thesusis.net>
To: Bernd Lentes <bernd.lentes@helmholtz-muenchen.de>
Cc: Andrei Borzenkov <arvidjaar@gmail.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: rollback to a snapshot
Date: Wed, 07 Jun 2023 16:08:45 -0400 [thread overview]
Message-ID: <87zg5b821z.fsf@vps.thesusis.net> (raw)
In-Reply-To: <PR3PR04MB7340EB60FBF52F117181580ED653A@PR3PR04MB7340.eurprd04.prod.outlook.com>
Bernd Lentes <bernd.lentes@helmholtz-muenchen.de> writes:
> Could you propose a setup here which does not use top level subvolumes ?
> I found it very frustrating that everyone says "BTRFS is great, you can do snapshots and easily rollback".
> Because in reality rollback is not easy. How can i avoid to use top level subvolumes ?
> I have some Suse boxes which seem to have a correct default setup. But when i install e.g. an Ubuntu box
> i really don't know how to setup BTRFS manually.
> There was a great Wiki (https://archive.kernel.org/oldwiki/btrfs.wiki.kernel.org/index.php/Main_Page.html),
> but now it's outdated. Is there something new ?
The last time I installed Ubuntu on btrfs, the installer automatically
created a top level subvolume named @ and actually installed the system
in that subvolume, then configured grub to tell the kernel to mount the
root btrfs volume with the flag subvol="@" so that the system would boot
normally. Then you just mount the real root of the filesystem somewhere
else and make a snapshot of the @ subvolume. When you want to roll
back, you just rename @ to something else, and either rename or create a
new writable snapshot from your previous snapshot and name it @, then
reboot.
next prev parent reply other threads:[~2023-06-07 20:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 20:58 rollback to a snapshot Bernd Lentes
2023-06-06 23:20 ` Eldon
2023-06-07 4:36 ` Andrei Borzenkov
2023-06-07 10:38 ` Bernd Lentes
2023-06-07 11:51 ` Andrei Borzenkov
2023-06-07 20:08 ` Phillip Susi [this message]
2023-06-07 20:51 ` Bernd Lentes
2023-06-07 22:18 ` Nicholas D Steeves
2023-06-08 19:39 ` Bernd Lentes
2023-06-08 20:09 ` Bernd Lentes
2023-06-13 16:01 ` Bernd Lentes
2023-06-07 10:45 ` Bernd Lentes
2023-06-07 16:35 ` Andrei Borzenkov
2023-06-07 19:37 ` Bernd Lentes
2023-06-07 19:46 ` remi
2023-06-07 20:07 ` Bernd Lentes
2023-06-07 20:14 ` Bernd Lentes
2023-06-07 20:48 ` Roman Mamedov
2023-06-07 21:00 ` Bernd Lentes
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=87zg5b821z.fsf@vps.thesusis.net \
--to=phill@thesusis.net \
--cc=arvidjaar@gmail.com \
--cc=bernd.lentes@helmholtz-muenchen.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