[TuxOnIce-users] dmcrypt and tuxonice , last file system mount time changed

[Nigel Cunningham]

Hi Aaron.

Sorry for the delay in getting back to you.

To see what's going on with the allocations (causing that backtrace at 
21 seconds), I've prepared a patch that will let you trace just that 
allocation. To use it, apply the patch, build, compile and install, then 
hibernate and when trying to resume, add toi_trace_allocs=38 to your 
commandline. You'll get a stack dump when the counters are reset, and 
for each allocation and free. There shouldn't be many of them.

Regarding /dev/sda8, is that your initrd? Going from the 
"initrd_devices=/dev/sda8" in the commandline you mentioned, and looking 
at the debugging info, it seems like everything is working correctly - 
just not as you desire. If /dev/sda8 is your initrd, is it possible for 
you to unmount it prior to hibernating? You will get corruption if you 
hibernate with it mounted, then mount it at resume time (thereby 
replaying the journal), then resume an image that no longer matches 
what's on disk (because of the journal replay).

Regards,

Nigel

PS: Sorry if you get this twice - I realised after clicking send that I 
was sending only to you, not to the list, and clicked cancel, but 
perhaps you'll get a copy anyway.