From: Andrew Morton <akpm@osdl.org>
To: Ed Sweetman <ed.sweetman@wmich.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 journel aborted in 2.6.0-mm1
Date: Sun, 28 Dec 2003 17:24:50 -0800 [thread overview]
Message-ID: <20031228172450.413cfa5c.akpm@osdl.org> (raw)
In-Reply-To: <3FEF5E53.1080203@wmich.edu>
Ed Sweetman <ed.sweetman@wmich.edu> wrote:
>
> Not sure what the cause of this type of error is but i've only seen it
> in the very late test releases of 2.6.0 and now in the mm1 patch (i've
> always used the mm branch of the test releases). It seems to like to
> happen to my partition that has /var/ on it during an updatedb and log
> rotate that is standard practice in most distributions. I'm using debian
> unstable if that helps narrow the problem down, however it seems more
> likely to be a kernel problem possibly in one of the patches that's been
> in mm's tree for very recent test, and now release, kernels.
>
I'd need to see the kernel logs at the time when the abort happens.
An internal filesystem inconsistency will certainly cause this. Force a
fsck.
prev parent reply other threads:[~2003-12-29 1:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 22:50 ext3 journel aborted in 2.6.0-mm1 Ed Sweetman
2003-12-29 1:24 ` Andrew Morton [this message]
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=20031228172450.413cfa5c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ed.sweetman@wmich.edu \
--cc=linux-kernel@vger.kernel.org \
/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