From: Martin Steigerwald <ms@teamix.de>
To: tuxonice-devel@lists.tuxonice.net, linux-kernel@vger.kernel.org
Cc: Nigel Cunningham <ncunningham@crca.org.au>
Subject: Re: [TuxOnIce-devel] safe resuming: automatically invalidating an outdated hibernate snapshot
Date: Mon, 13 Oct 2008 13:35:25 +0200 [thread overview]
Message-ID: <200810131335.25793.ms@teamix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]
Am Montag, 13. Oktober 2008 schrieben Sie:
> Hi Martin.
Hi Nigel,
> On Mon, 2008-10-13 at 12:13 +0200, Martin Steigerwald wrote:
> > Cc to linux-kernel: This is mainly for tuxonice, but it might also be
> > relevant for other hibernate implementations. Maybe some general
> > mechanism for checking whether an on disk snapshot of the system is
> > current would be good - as also the resume parameter could be missing or
> > wrong or whatnot.
> >
> >
> > Hi!
> >
> > Is there a way to automatically invalidate the tuxonice snapshot when a
> > non tuxonice kernel is booted accidentally? I.e. could tuxonice recognize
> > when the swap partition has been accessed *after* the snapshot has been
> > written?
[...]
> The simplest way is to mkswap the appropriate partitions from a script
> run when booting (after we check whether to resume, of course). I
> believe the hibernate script already has support for this. Maybe
> pm-utils or such like needs it too?
Simple idea. But I dislike automatically formatting a partition on each boot.
What if the user changes the partition layout and forgets to adapt swap
partition / resume parameter? AFAIR only mkfs.xfs really checks whether the
partition contains an existing filesystem and even that check does cannot
trigger in case an undetected filesystem is on the partition.
Thus I'd prefer a way to touch the swap partition without destroying its
contents and then checking whether it has been touched after the snapshot has
been written. I would then like to have it touched on every bootup on the
Linux system. Would something along these lines be possible?
Ciao,
--
Martin Steigerwald - team(ix) GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-10-13 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 11:35 Martin Steigerwald [this message]
2008-10-13 20:41 ` [TuxOnIce-devel] safe resuming: automatically invalidating an outdated hibernate snapshot Nigel Cunningham
2008-10-16 10:33 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2008-10-13 10:13 Martin Steigerwald
2008-10-13 11:13 ` [TuxOnIce-devel] " Nigel Cunningham
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=200810131335.25793.ms@teamix.de \
--to=ms@teamix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@crca.org.au \
--cc=tuxonice-devel@lists.tuxonice.net \
/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