From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Nigel Cunningham <ncunningham@clear.net.nz>
Cc: Andrew Morton <akpm@digeo.com>, Pavel Machek <pavel@suse.cz>,
cat@zip.com.au, mbligh@aracnet.com, gigerstyle@gmx.ch,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fix SWSUSP & !SWAP
Date: Thu, 24 Apr 2003 13:36:46 +0200 (MEST) [thread overview]
Message-ID: <Pine.GSO.4.21.0304241335210.19942-100000@vervain.sonytel.be> (raw)
In-Reply-To: <1051182797.2250.10.camel@laptop-linux>
On Thu, 24 Apr 2003, Nigel Cunningham wrote:
> On Thu, 2003-04-24 at 21:46, Andrew Morton wrote:
> > > > Sorry, I still don't get it. Go through the steps for me:
> > > >
> > > > 1) suspend writes pages to disk
> > > >
> > > > 2) machine is shutdown
> > > >
> > > > 3) restart, journal replay
>
> Corruption comes here. The journal reply tidies things up that shouldn't
> be tidied up. They shouldn't be tidied up because once we reload the
> image, things should be in the same state as prior to suspend. If replay
> frees a block (thinking it wasn't properly linked or something similar),
> it introduces corruption.
This has nothing to do with using a swapfile.
But if you resume from swsusp, you don't really `mount' all file systems. They
are implicitly mounted because they were mounted before the suspend operation.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2003-04-24 11:25 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 13:51 Fix SWSUSP & !SWAP Pavel Machek
2003-04-23 14:32 ` Geert Uytterhoeven
2003-04-23 14:47 ` Pavel Machek
2003-04-23 15:56 ` gigerstyle
2003-04-23 19:41 ` Nigel Cunningham
2003-04-23 20:36 ` Marc Giger
2003-04-23 22:25 ` Nigel Cunningham
2003-04-23 23:28 ` Martin J. Bligh
2003-04-23 23:58 ` Pavel Machek
2003-04-23 23:55 ` Martin J. Bligh
2003-04-24 0:07 ` Andrew Morton
2003-04-24 0:17 ` CaT
2003-04-24 0:16 ` Nigel Cunningham
2003-04-24 0:26 ` Randy.Dunlap
2003-04-24 0:31 ` CaT
2003-04-24 0:38 ` Andrew Morton
2003-04-24 0:54 ` CaT
2003-04-24 1:06 ` Andrew Morton
2003-04-24 8:48 ` John Bradford
2003-04-24 0:37 ` Andrew Morton
2003-04-24 9:12 ` Pavel Machek
2003-04-24 9:25 ` Andrew Morton
2003-04-24 9:35 ` Pavel Machek
2003-04-24 9:46 ` Andrew Morton
2003-04-24 11:13 ` Nigel Cunningham
2003-04-24 11:36 ` Andrew Morton
2003-04-24 14:26 ` Pavel Machek
2003-04-24 16:37 ` Andreas Dilger
2003-04-24 20:48 ` Pavel Machek
2003-04-24 21:46 ` Andreas Dilger
2003-04-25 1:09 ` Nigel Cunningham
2003-04-25 12:59 ` Pavel Machek
2003-04-25 16:20 ` Andreas Dilger
2003-04-25 18:28 ` Nigel Cunningham
2003-04-25 19:32 ` Jamie Lokier
2003-04-25 19:58 ` Andreas Dilger
2003-04-27 18:59 ` Pavel Machek
2003-04-24 11:36 ` Geert Uytterhoeven [this message]
2003-04-25 1:22 ` H. Peter Anvin
2003-04-25 1:19 ` Nigel Cunningham
2003-04-25 1:31 ` Hua Zhong
2003-04-25 19:41 ` H. Peter Anvin
2003-04-25 4:27 ` Andreas Dilger
2003-04-25 4:33 ` H. Peter Anvin
2003-04-24 0:25 ` Pavel Machek
2003-04-24 9:01 ` Andrew Morton
2003-04-24 9:14 ` Pavel Machek
2003-04-24 9:05 ` Jamie Lokier
2003-04-24 9:34 ` Pavel Machek
2003-04-24 15:22 ` Carl-Daniel Hailfinger
2003-04-24 8:00 ` Marc Giger
2003-04-23 23:47 Grover, Andrew
2003-04-24 0:03 ` Pavel Machek
2003-04-23 23:57 ` Martin J. Bligh
2003-04-24 0:25 ` Pavel Machek
2003-04-24 0:37 ` CaT
2003-04-24 0:49 ` Martin J. Bligh
2003-04-24 9:16 ` Pavel Machek
2003-04-24 0:02 ` Nigel Cunningham
2003-04-24 0:23 ` Pavel Machek
2003-04-24 0:45 ` Martin J. Bligh
2003-04-24 3:17 ` Nigel Cunningham
2003-04-24 4:37 ` Martin J. Bligh
2003-04-24 7:49 ` Marc Giger
2003-04-24 9:27 ` Pavel Machek
2003-04-24 3:49 ` David Ford
2003-04-24 6:54 ` Jörn Engel
2003-04-24 7:01 ` Elladan
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=Pine.GSO.4.21.0304241335210.19942-100000@vervain.sonytel.be \
--to=geert@linux-m68k.org \
--cc=akpm@digeo.com \
--cc=cat@zip.com.au \
--cc=gigerstyle@gmx.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=ncunningham@clear.net.nz \
--cc=pavel@suse.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;
as well as URLs for NNTP newsgroup(s).