From: Mario Mikocevic <mozgy@hinet.hr>
To: Michael Clark <michael@metaparadigm.com>
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 11:21:52 +0200 [thread overview]
Message-ID: <20020926092152.GA32593@danielle.hinet.hr> (raw)
In-Reply-To: <3D92BDC8.8080603@metaparadigm.com>
Hi,
slightly trimmed,
On Thu, Sep 26, 2002 at 03:56:56PM +0800, Michael Clark wrote:
> On 09/26/02 15:27, Andrew Morton wrote:
>
> >People are saying unkind things about the qlogic driver, and
>
> Yes i know. My experience seems to be bad fault recovery after
> a LIP reset although the driver in 2.4.19pre10aa4 seems okay
> (have tested loop interruption under IO heavy load).
>
> >the new version in Andrea's latest patchset is definitely
> >faster than before. Might be worth a shot.
>
> 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
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)
--
Mario Mikočević (Mozgy)
mozgy at hinet dot hr
My favourite FUBAR ...
next prev parent reply other threads:[~2002-09-26 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 5:57 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 [this message]
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=20020926092152.GA32593@danielle.hinet.hr \
--to=mozgy@hinet.hr \
--cc=akpm@digeo.com \
--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
Powered by JetHome