From: Calvin Walton <calvin.walton@kepstin.ca>
To: Richard Hughes <hughsient@gmail.com>
Cc: Leonidas Spyropoulos <artafinde@gmail.com>,
Hugo Mills <hugo@carfax.org.uk>,
linux-btrfs@vger.kernel.org
Subject: Re: Naming of subvolumes
Date: Thu, 25 Oct 2012 11:59:50 -0400 [thread overview]
Message-ID: <1351180790.740.11.camel@ayu> (raw)
In-Reply-To: <1351178178.1923.12.camel@hughsie-work.lan>
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
On Thu, 2012-10-25 at 16:16 +0100, Richard Hughes wrote:
> On Thu, 2012-10-25 at 16:09 +0100, Leonidas Spyropoulos wrote:
> > On another note. How would you implement that logic (make a snapshot
> > before upgrade) without the lib? Would you wrap package manager into a
> > wrapper or patch package manager to call snapshot and the upgrade.
> > In both cases you will need to parse stdout, stderr from the snapshot
> > creation.
>
> I'm intending to add the snapshot stuff in the logic described here:
> https://gitorious.org/packagekit/packagekit/blobs/master/contrib/systemd-updates/README.txt
>
> > Also would you automatically roll back to before snapshot if something
> > goes wrong or give option to user? Can you categorise errors on
> > upgrades according ti fatality to the system?
>
> If *anything* in the upgrade fails and we've already started the package
> transaction then we'd roll back to the previous known-good snapshot.
Rolling back to a previous snapshot would require either a reboot or
using something like rsync to copy the old state back to the currently
mounted subvolume, unfortunately. There's no provision in Linux to allow
switching out the mounted filesystem from under running applications :)
--
Calvin Walton <calvin.walton@kepstin.ca>
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4027 bytes --]
next prev parent reply other threads:[~2012-10-25 15:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 12:30 Naming of subvolumes Richard Hughes
2012-10-25 13:18 ` anand jain
2012-10-25 13:28 ` Hugo Mills
2012-10-25 13:44 ` Richard Hughes
[not found] ` <CAAeznTr6AvqbJ+WOw6S5kyW2_qbSUQgJfAO88m9KdV+3PyGUcw@mail.gmail.com>
2012-10-25 15:16 ` Richard Hughes
2012-10-25 15:59 ` Calvin Walton [this message]
2012-10-25 17:19 ` Richard Hughes
2012-10-26 5:24 ` Chris Murphy
2012-10-26 8:27 ` Richard Hughes
2012-10-26 15:54 ` Chris Murphy
2012-10-27 1:58 ` cwillu
2012-10-27 3:03 ` Fajar A. Nugraha
2012-10-27 17:22 ` Naming of (bootable) subvolumes Chris Murphy
2012-10-28 9:25 ` Goffredo Baroncelli
2012-10-28 16:57 ` Chris Murphy
2012-10-28 9:38 ` Fajar A. Nugraha
2012-10-27 16:08 ` Naming of subvolumes 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=1351180790.740.11.camel@ayu \
--to=calvin.walton@kepstin.ca \
--cc=artafinde@gmail.com \
--cc=hughsient@gmail.com \
--cc=hugo@carfax.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).