All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: rootfs snapshots and rollback (i.e. testing updates)
Date: Mon, 09 Nov 2009 11:38:19 -0500	[thread overview]
Message-ID: <m3639jk610.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <4AF82E78.1010200@wpkg.org> (Tomasz Chmielewski's message of "Mon, 09 Nov 2009 16:00:08 +0100")

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.

An obvious way to make this nicer would be to:
   * have the package manager create the snapshot before modifying the
     system, with a timestamp.
   * modify the bootloader to give a choice of snapshots at boot-time.

Note that you're rolling back *all* rootfs changes, not merely the
changes that the package manager made, so it wouldn't be correct to
think of this as a way to only rollback package manager transactions.

- Chris.
-- 
Chris Ball   <cjb@laptop.org>
One Laptop Per Child

  parent reply	other threads:[~2009-11-09 16:38 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 [this message]
2009-11-10  9:53   ` Tomasz Chmielewski
2009-11-10 14:13     ` John Dong

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=m3639jk610.fsf@pullcord.laptop.org \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.