From: "Stephen C. Tweedie" <sct@redhat.com>
To: Lukasz Trabinski <lukasz@wsisiz.edu.pl>
Cc: ext3 users list <ext3-users@redhat.com>,
akpm@zip.com.au, Andreas Dilger <adilger@clusterfs.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-pre3 - problems with ext3
Date: 20 Jan 2003 22:38:17 +0000 [thread overview]
Message-ID: <1043102297.13050.59.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.51.0301141401260.6636@oceanic.wsisiz.edu.pl>
Hi,
On Tue, 2003-01-14 at 13:15, Lukasz Trabinski wrote:
> Since 2.4.20, we have problems with ext3. Machine is 2xPentium III (1GHz),
> 2GB RAM, 1GB swap. RH 8.0 (glibc-2.3.1-21), gcc (GCC) 3.2 20020903
So it was stable under earlier kernels?
> Is it a problem with ext3 or problems with disk (hardware problem) or
> something else?
There's nothing in the trace to indicate a hardware fault. Is there
anything else showing up in the logs which might indicate the kernel
getting into a tangle?
>From the assert failure:
> Jan 14 12:53:52 oceanic kernel: Assertion failure in
> journal_start_Rsmp_909c88ec() at transaction.c:249:
> "handle->h_transaction->t_journal == journal"
it looks as if either the VM has been recursing into the filesystem
(filesystem problem or a missing GFP_NOFS somewhere), or there has been
a stack overflow (the data structure that the mismatch is on is just
about the very last thing on the task structure that the stack grows
towards.)
But as for the decoded OOPS, I can't immediately trace through it
successfully. There's no syscall entry point at the top of the stack,
and there appear to be two separate possible interpretations of the call
trace. Do you have any other captured oopses that I might be able to
find some common threads in?
Cheers,
Stephen
next prev parent reply other threads:[~2003-01-20 22:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 13:15 Lukasz Trabinski
2003-01-14 15:15 ` Stephen C. Tweedie
2003-01-14 15:48 ` Lukasz Trabinski
2003-01-20 22:38 ` Stephen C. Tweedie [this message]
2003-01-21 0:25 ` 2.4.21-pre3 - problems with ext3 (long) Lukasz Trabinski
2003-01-21 13:56 ` Stephen C. Tweedie
2003-01-21 14:22 ` Bartlomiej Solarz-Niesluchowski
2003-01-21 14:38 ` Stephen C. Tweedie
2003-01-21 14:54 ` Bartlomiej Solarz-Niesluchowski
2003-02-06 15:47 ` Bartlomiej Solarz-Niesluchowski
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=1043102297.13050.59.camel@sisko.scot.redhat.com \
--to=sct@redhat.com \
--cc=adilger@clusterfs.com \
--cc=akpm@zip.com.au \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz@wsisiz.edu.pl \
/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
all inboxes | Powered by JetHome®