From: Andreas Dilger <adilger@turbolabs.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: Pavel Machek <pavel@ucw.cz>, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: swsusp: move resume before mounting root [diff against vanilla 2.4.9]
Date: Wed, 26 Sep 2001 22:29:06 -0600 [thread overview]
Message-ID: <20010926222906.J1140@turbolinux.com> (raw)
In-Reply-To: <20010926101914.A28339@atrey.karlin.mff.cuni.cz> <200109270302.f8R32pl12537@saturn.cs.uml.edu>
In-Reply-To: <200109270302.f8R32pl12537@saturn.cs.uml.edu>
On Sep 26, 2001 23:02 -0400, Albert D. Cahalan wrote:
> That is totally broken, because I may mount the disk in between
> the suspend and resume. I might even:
>
> 1. boot kernel X
> 2. suspend kernel X
> 3. boot kernel Y
> 4. suspend kernel Y
> 5. resume kernel X
> 6. suspend kernel X
> 7. resume kernel Y
> 8. suspend kernel Y
> 9. goto #5
>
> You really have to close the logs and mark the disks clean
> when you suspend. The problems here are similar the the ones
> NFS faces. Between the suspend and resume, filesystems may be
> modified in arbitrary ways.
This is possible with the "write_super_lockfs" interface to the
journaling filesystems (ext3/reiserfs/XFS). This is normally
used for LVM snapshots, but it could also be used for this.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-09-27 4:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 16:42 swsusp: move resume before mounting root [diff against vanilla 2.4.9] Pavel Machek
[not found] ` <200109260602.f8Q62TM420328@saturn.cs.uml.edu>
2001-09-26 8:19 ` Pavel Machek
2001-09-27 3:02 ` Albert D. Cahalan
2001-09-27 4:29 ` Andreas Dilger [this message]
2001-09-27 4:51 ` Tim Connors
2001-09-29 22:23 ` Pavel Machek
2001-09-27 14:34 ` swsusp: move " Pavel Machek
2001-09-28 3:56 ` Albert D. Cahalan
2001-09-28 20:40 ` Pavel Machek
2001-09-29 7:55 ` Albert D. Cahalan
2001-09-29 8:40 ` Pavel Machek
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=20010926222906.J1140@turbolinux.com \
--to=adilger@turbolabs.com \
--cc=acahalan@cs.uml.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox