[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20081016103338.GB1563@ucw.cz>
Date: Thu, 16 Oct 2008 12:33:38 +0200
From: Pavel Machek <pavel@...e.cz>
To: Martin Steigerwald <ms@...mix.de>
Cc: tuxonice-devel@...ts.tuxonice.net, linux-kernel@...r.kernel.org,
Nigel Cunningham <ncunningham@...a.org.au>
Subject: Re: [TuxOnIce-devel] safe resuming: automatically invalidating an
outdated hibernate snapshot
On Mon 2008-10-13 13:35:25, Martin Steigerwald wrote:
> 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
Simple solution: add --only-mkswap-when-its-hibernation-image option
to mkswap.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists