From: John Dong <jdong@ubuntu.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: Chris Ball <cjb@laptop.org>, linux-btrfs@vger.kernel.org
Subject: Re: rootfs snapshots and rollback (i.e. testing updates)
Date: Tue, 10 Nov 2009 09:13:36 -0500 [thread overview]
Message-ID: <43C29220-06F4-4B19-B97F-BF587501F788@ubuntu.com> (raw)
In-Reply-To: <4AF9382A.60804@wpkg.org>
On Nov 10, 2009, at 4:53 AM, Tomasz Chmielewski wrote:
> Chris Ball wrote:
>> Hi,
>> > Is it possible, with current btrfs:
>> Yes, I think so.
>> > - to take a rootfs snapshot (i.e. prior to a major update),
>> btrfsctl -s newsnap /
>> > - do changes in the root filesystem (i.e. install major update),
>> > > - if we don't like what the major update did to the system
>> > (rootfs), "rollback" the snapshot and make it the "original"
>> > rootfs again (perhaps, with a reboot in between).
>> Before rebooting, edit whatever mounts your root partition (initrd,
>> fstab, kernel argument) to add a "subvol=newsnap" mount argument.
>
> So, if I understand it correctly, it's not really "rolling back".
>
> Rather, with a "failed upgrade", we would mount a "newsnap" snapshot to use the old rootfs again.
>
>
> What's still left here would be:
>
> - remove the "failed upgrade" "(sub)volume" (which is "/" now?)
>
> - turn everything to such a state, so that you can mount the old/original rootfs without adding any "subvol=newsnap" mount arguments
>
>
> Correct me if I'm wrong.
You're right. What's needed is a way to set the new default subvol
prev parent reply other threads:[~2009-11-10 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 15:00 rootfs snapshots and rollback (i.e. testing updates) Tomasz Chmielewski
2009-11-09 16:24 ` John Dong
2009-11-09 16:38 ` Chris Ball
2009-11-10 9:53 ` Tomasz Chmielewski
2009-11-10 14:13 ` John Dong [this message]
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=43C29220-06F4-4B19-B97F-BF587501F788@ubuntu.com \
--to=jdong@ubuntu.com \
--cc=cjb@laptop.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=mangoo@wpkg.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