linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Michael Clark <michael@metaparadigm.com>
Cc: linux-kernel@vger.kernel.org, Andrea Arcangeli <andrea@suse.de>
Subject: Re: 2.4.19pre10aa4 OOPS in ext3 (get_hash_table,   unmap_underlying_metadata)
Date: Thu, 26 Sep 2002 01:02:20 -0700	[thread overview]
Message-ID: <3D92BF0C.DBDDFA38@digeo.com> (raw)
In-Reply-To: 3D92BDC8.8080603@metaparadigm.com

Michael Clark wrote:
> 
> On 09/26/02 15:27, Andrew Morton wrote:
> > Michael Clark wrote:
> >
> >>Hiya,
> >>
> >>Been having frequent (every 4-8 days) oopses with 2.4.19pre10aa4 on
> >>a moderately loaded server (100 users - 0.4 load avg).
> >>
> >>The server is a Intel STL2 with dual P3, 1GB RAM, Intel Pro1000T
> >>and Qlogic 2300 Fibre channel HBA.
> >>
> >>We are running qla2300, e1000 and lvm modules unmodified as present in
> >>2.4.19pre10aa4. We also have quotas enabled on 1 of the ext3 fs.
> >>
> >
> >
> > It's not familiar, sorry.
> 
> Maybe I should try XFS? I've heard of people running this for
> 80+ days and no downtime. I really would like to get past 8 days.

Well that would be one way of eliminating variables, and that's
the only way to narrow this down.   Looks like something somewhere
(software or hardware) has corrupted some memory.

The problem is that even if you _do_ fix the problem by switching
something out, the cause could lie elsewhere.

  reply	other threads:[~2002-09-26  7:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-26  5:57 2.4.19pre10aa4 OOPS in ext3 (get_hash_table, unmap_underlying_metadata) Michael Clark
2002-09-26  7:27 ` Andrew Morton
2002-09-26  7:56   ` Michael Clark
2002-09-26  8:02     ` Andrew Morton [this message]
2002-09-26 11:12       ` Andrea Arcangeli
2002-09-26 11:43         ` Michael Clark
2002-09-26  9:21     ` Mario Mikocevic
2002-09-26  9:53       ` Michael Clark
2002-09-26 11:13         ` Mario Mikocevic
2002-09-26 11:48           ` Michael Clark

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=3D92BF0C.DBDDFA38@digeo.com \
    --to=akpm@digeo.com \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@metaparadigm.com \
    /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).