headers
Martin Steigerwald | 13 Oct 12:12
Favicon

safe resuming: automatically invalidating an outdated hibernate snapshot

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?

It happened here several times that someone booted the wrong kernel and then 
someone else booted the right one again. TuxOnIce would then resume from a 
snapshot that it not up-to-date anymore. This leads to filesystem breakage as 
the filesystem slab objects and other in memory structures would not 
represent the current state of the filesystem on disk. xfs_repair did a 
marvellous job on these occassions and I already changed menu.lst to hide the 
GRUB boot menu by default, but it would be better if this case of  
maloperation can be intercepted.

Ciao,
--

-- 
Martin Steigerwald - team(ix) GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90

_______________________________________________
TuxOnIce-devel mailing list
TuxOnIce-devel <at> lists.tuxonice.net
http://lists.tuxonice.net/mailman/listinfo/tuxonice-devel
(Continue reading)

Permalink | Reply |
headers
Nigel Cunningham | 13 Oct 13:13
Favicon

Re: safe resuming: automatically invalidating an outdated hibernate snapshot

Hi Martin.

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?
> 
> It happened here several times that someone booted the wrong kernel and then 
> someone else booted the right one again. TuxOnIce would then resume from a 
> snapshot that it not up-to-date anymore. This leads to filesystem breakage as 
> the filesystem slab objects and other in memory structures would not 
> represent the current state of the filesystem on disk. xfs_repair did a 
> marvellous job on these occassions and I already changed menu.lst to hide the 
> GRUB boot menu by default, but it would be better if this case of  
> maloperation can be intercepted.

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?

Nigel
(Continue reading)

Permalink | Reply |
headers
Martin Steigerwald | 13 Oct 13:33
Favicon

Re: safe resuming: automatically invalidating an outdated hibernate snapshot

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
(Continue reading)

Permalink | Reply |
headers
Nigel Cunningham | 13 Oct 22:41
Favicon

Re: safe resuming: automatically invalidating an outdated hibernate snapshot

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?
>
(Continue reading)

Permalink | Reply |
headers
Pavel Machek | 16 Oct 12:33
Favicon

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
(Continue reading)

Permalink | Reply |

Gmane