From: Bas Mevissen <ml@basmevissen.nl>
To: ncunningham@users.sourceforge.net
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Jan Dittmer <j.dittmer@portrix.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ext3 on raid5 failure
Date: Wed, 04 Feb 2004 12:38:13 +0100 [thread overview]
Message-ID: <4020D9A5.2040109@basmevissen.nl> (raw)
In-Reply-To: <1075887812.2518.125.camel@laptop-linux>
Nigel Cunningham wrote:
> Hi.
>
> Are you using a swap partition or swap file? If we're talking swap file,
> I would suspect suspend2. I haven't had a chance to look yet (preparing
> to move to Aussie), but Michael has told me there are problems with the
> swapfile support.
>
You are reading everything, I beleave :-)
Nope, only a swap partition. I read swsusp ML too :-)
I really suspect the power failure (forgot to plug in the AC adapter :-)
) was the "hard off" with the FS corruption.
> If you had a crash while using suspend and swap file support, I wouldn't
> be totally surprised to see an emergency sync causing this. That said,
> the code has a number of safety nets aimed at stopping us syncing while
> suspend is running, to avoid precisely this sort of corruption. If it
> was suspend, I'd expect your superblock to have been messed too. Did
> that happen?
>
The superblock was fine. There was just a short file system check when
booting again. I only noticed it a day later when the news reader didn't
want to start anymore.
But thanks for thinking!
Regards,
Bas.
next prev parent reply other threads:[~2004-02-04 11:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 10:27 Jan Dittmer
2004-01-18 18:02 ` Mike Fedyk
2004-01-19 15:30 ` Theodore Ts'o
2004-01-23 8:22 ` Jan Dittmer
2004-01-27 19:08 ` Theodore Ts'o
2004-01-28 10:54 ` Jan Dittmer
2004-01-29 11:44 ` Theodore Ts'o
2004-02-04 9:24 ` Bas Mevissen
2004-02-04 9:43 ` Nigel Cunningham
2004-02-04 11:38 ` Bas Mevissen [this message]
2004-02-04 20:49 ` Nigel Cunningham
2004-02-17 23:14 ` Pavel Machek
2004-02-17 23:58 ` Kiko Piris
2004-02-06 19:18 ` Theodore Ts'o
2004-02-09 8:55 ` Bas Mevissen
2004-02-18 3:07 ` Bill Davidsen
2004-02-19 9:27 ` Bas Mevissen
2004-02-19 19:47 ` Bill Davidsen
2004-01-28 11:06 ` Jan Dittmer
2004-02-19 2:32 ` Leandro Guimarães Faria Corsetti Dutra
2004-02-19 8:07 ` Jan Dittmer
2004-02-19 13:50 ` Leandro Guimarães Faria Corcete Dutra
2004-02-19 14:58 ` Leandro Guimarães Faria Corsetti Dutra
2004-02-25 17:45 Muhammad L.
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=4020D9A5.2040109@basmevissen.nl \
--to=ml@basmevissen.nl \
--cc=j.dittmer@portrix.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@users.sourceforge.net \
--cc=tytso@mit.edu \
/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
Powered by JetHome