Re: [TuxOnIce-devel] safe resuming: automatically invalidating anoutdated hibernate snapshot

[Nigel Cunningham]

Hi Martin.

On Mon, 2008-10-13 at 13:35 +0200, 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 
> 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?

The only way around this issue that I can see would be if we could get
the last mount time of each partition without doing any writes to that
partition. We could then record those times in the image header and
compare them at boot. Unfortunately, however - as far as I know -
there's no support for that at the moment.

Regards,

Nigel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/