On Mon, Sep 05, 2005 at 10:27:35AM +0200, Pavel Machek wrote: > > There's a better reason, too. I do swsusp. Then I'd like to boot with > / mounted read-only (so that I can read my config files, some > binaries, and maybe suspended image), but I absolutely may not write > to disk at this point, because I still want to resume. > You could _hope_ that the filesystem is consistent enough that it is safe to try to read config files, binaries, etc. without running the journal, but there is absolutely no guarantee that this is the case. I'm not sure you want to depend on that for swsusp. One potential solution that would probably meet your needs is a dm hack which reads in the blocks in the journal, and then uses the most recent block in the journal in preference to the version on disk. - Ted -- Linux-cluster@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/linux-cluster
