From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Nigel Cunningham <nigel@suspend2.net>,
linux-pm@osdl.org, linux-pm@lists.osdl.org, "Victor Porton, , ,
" <porton@ex-code.com>
Subject: Re: Re: standby to disk transition
Date: Tue, 14 Mar 2006 21:33:50 +0100 [thread overview]
Message-ID: <20060314203350.GG1782@elf.ucw.cz> (raw)
In-Reply-To: <200603140036.17051.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
Hi!
> > We need to be able to rollback the state of the filesystem in memory and on
> > disk to the point where the last checkpoint was made. Memory would be
> > straight forward if we want to do it dumbly and slowly - just reload the
> > whole check pointed image. If we want to be more efficient, we'd want to just
> > load the pages that had changed (Mark on (first) write?). But filesystems
> > seem to be a whole different story. Do any of the commonly used fses have
> > support for checkpointing and rollback back at the moment?
>
> I'm not sure if we need a rollback as such. What we need is to make sure
> the filesystems state will be consistent before as well as after we have
> "reloaded" the snapshot.
Even if you make sure *kernel* is consistent with changed filesystem,
userland is going to be badly confused. Imagine what will happen with
memory mapped files, for example.
I'm not sure how it could work...
Pavel
--
130: Buffer.BlockCopy( sbuffer, Pos + 4, Bytes, 0, Bytes.Length );
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2006-03-14 20:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 2:34 standby to disk transition Victor Porton,,,
2006-03-13 8:30 ` Pavel Machek
2006-03-13 8:48 ` Adam Belay
2006-03-13 8:50 ` Pavel Machek
2006-03-13 9:07 ` Adam Belay
2006-03-13 9:13 ` Pavel Machek
2006-03-13 18:33 ` Dave Jones
2006-03-13 21:24 ` Pavel Machek
2006-03-13 21:28 ` Dave Jones
2006-03-13 21:46 ` Pavel Machek
2006-03-13 22:06 ` Rafael J. Wysocki
2006-03-13 21:59 ` Nigel Cunningham
2006-03-13 22:08 ` Pavel Machek
2006-03-13 22:42 ` Rafael J. Wysocki
2006-03-13 23:11 ` Nigel Cunningham
2006-03-13 23:36 ` Rafael J. Wysocki
2006-03-14 0:18 ` Nigel Cunningham
2006-03-14 18:12 ` Rafael J. Wysocki
2006-03-14 20:33 ` Pavel Machek [this message]
2006-03-14 21:13 ` Rafael J. Wysocki
2006-03-14 21:22 ` Pavel Machek
2006-03-14 21:42 ` Alan Stern
2006-03-14 22:07 ` Rafael J. Wysocki
2006-03-15 15:14 ` Alan Stern
2006-03-14 21:57 ` Rafael J. Wysocki
2006-03-14 21:59 ` Pavel Machek
2006-03-15 0:22 ` suspend-to-both [was Re: Re: standby to disk transition] Pavel Machek
2006-03-14 20:29 ` Re: standby to disk transition Pavel Machek
2006-03-14 0:21 ` Nigel Cunningham
2006-03-14 9:50 ` Pavel Machek
2006-03-13 13:55 ` 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=20060314203350.GG1782@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-pm@lists.osdl.org \
--cc=linux-pm@osdl.org \
--cc=nigel@suspend2.net \
--cc=porton@ex-code.com \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.