From: Michael Clark <michael@metaparadigm.com>
To: Mario Mikocevic <mozgy@hinet.hr>
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19pre10aa4 OOPS in ext3 (get_hash_table, unmap_underlying_metadata)
Date: Thu, 26 Sep 2002 17:53:38 +0800 [thread overview]
Message-ID: <3D92D922.5000606@metaparadigm.com> (raw)
In-Reply-To: 20020926092152.GA32593@danielle.hinet.hr
On 09/26/02 17:21, Mario Mikocevic wrote:
[snip]
>>So, is possible for qlogic driver to be doing naughty things
>>with bufferheads? or is it more likely in the fs?
>>
>>Anyone out there running a reasonably busy fileserver with
>>qlogic FC HBA and using ext3 or XFS with quotas? What
>>kernel/qlogic driver combo?
>
>
> # w
> 11:06am up 159 days, 12:01, 1 user, load average: 4.22, 3.41, 3.53
> # uname -r
> 2.4.18
I wish i had that uptime - reminds me of my 2.2.x boxes
(although they don't have ext3 or qlogic HBAs).
> ext3 partition on SAN connected through _two_ qla2200 HBAs and onto _two_
> FC switches with qla2200phase1.tar.gz driver from Arjan van de Ven.
> (the _only_ driver that works with MULTIPATH)
This linus 2.4.18? just with qlogic driver added?
I wonder if LVM has anything to do with my problems,
you using quotas or LVM?
Also I wonder if the file access pattern of 'afpd' (the offending
process in my oops) triggers some problem not usually observed.
~mc
next prev parent reply other threads:[~2002-09-26 9:48 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
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 [this message]
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=3D92D922.5000606@metaparadigm.com \
--to=michael@metaparadigm.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mozgy@hinet.hr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.