All of lore.kernel.org
 help / color / mirror / Atom feed
From: GrandMasterLee <masterlee@digitalroadkill.net>
To: Michael Clark <michael@metaparadigm.com>
Cc: Simon Roscic <simon.roscic@chello.at>, linux-kernel@vger.kernel.org
Subject: Re: [Kernel 2.5] Qlogic 2x00 driver
Date: 16 Oct 2002 23:08:04 -0500	[thread overview]
Message-ID: <1034827683.26.76.camel@localhost> (raw)
In-Reply-To: <3DAE3465.6060006@metaparadigm.com>

On Wed, 2002-10-16 at 22:54, Michael Clark wrote:
> On 10/17/02 11:12, GrandMasterLee wrote:
> > On Wed, 2002-10-16 at 11:49, Michael Clark wrote:
> >>Seems to be the correlation so far. qlogic driver without lvm works okay.
> >>qlogic driver with lvm, oopsorama.
> > 
> > 
> > Michael, what exactly do your servers do? Are they DB servers with ~1Tb
> > connected, or file-servers with hundreds of gigs, etc?
> 
> My customer currently has about 400Gb on this particular 4 node Application
> cluster (actually 2 x 2 node clusters using kimberlite HA software).
> 
> It has 11 logical hosts (services) spread over the 4 nodes with services such
> as Oracle 8.1.7, Oracle Financials (11i), a busy openldap server, and busy
> netatalk AppleShare Servers, Cyrus IMAP server. All are on ext3 partitions
> and were previously using LVM to slice up the storage.

On each of the Nodes, correct?

> The cluster usually has around 200-300 active users.
> 
> We have had oops (in ext3) on differing logical hosts which where running
> different services. ie. has oopsed on the node mastering the fileserver,
> and also on the node mastering the oracle database.

And again, each was running LVM in a shared storage mode for failover?

> Cross fingers, since removing LVM (which was the only change we have made,
> same kernel) we have had 3 times our longest uptime and still counting.
> 
> By the sounds, from earlier emails I had posted, users had responded
> to me who were also using qlogic and none of them had had any problems,
> the key factor was none of them were running LVM - this is what made
> me think to try and remove it (it was really just a hunch). We had
> gone through months of changing kernel versions, changing GigE network
> adapters, driver versions, etc, to no avail, then finally the LVM removal.

Kewl. That makes me feel much better now too. 

> Due to the potential nature of it being a stack problem. The problem
> really can't just be pointed at LVM but more the additive effect this
> would have on some underlying stack problem.
> 
> I believe the RedHat kernels i tried (rh7.2 2.4.9-34 errata was the most
> recent) also had this 'stack' problem. I am currently using 2.4.19pre10aa4.

Kewl. I'm using 2.4.19-aa1 (rc5-aa1, but hell, it's the same thing).

> I would hate to reccomend you remove LVM and it not work, but i
> must say it has worked for me (i'm just glad i didn't go to XFS instead
> of removing LVM as i did - as this was the other option i was pondering).

I hear you. We were pondering changing to EXT3, and not just EXT3, RHAS
also. i.e. more money, unknown kernel config, etc. I was going to be
*very* upset.  Are you running FC2(qla2300Fs in FC2 config) or FC1?

TIA

> ~mc
> 

  reply	other threads:[~2002-10-17  4:02 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 19:20 [Kernel 2.5] Qlogic 2x00 driver Simon Roscic
2002-10-15 19:31 ` Arjan van de Ven
2002-10-15 19:53   ` Simon Roscic
2002-10-16  2:51     ` Michael Clark
2002-10-16  3:56       ` GrandMasterLee
2002-10-16  4:30         ` Michael Clark
2002-10-16  4:35           ` J Sloan
2002-10-16  4:43             ` GrandMasterLee
2002-10-16  6:03               ` Michael Clark
2002-10-16  6:31                 ` GrandMasterLee
2002-10-16  6:40                   ` Michael Clark
2002-10-16  6:48                     ` GrandMasterLee
2002-10-16  6:59                       ` Michael Clark
2002-10-16  4:58             ` GrandMasterLee
2002-10-16  5:28             ` Michael Clark
2002-10-16  5:40               ` Andreas Dilger
2002-10-17  1:59                 ` Andrew Vasquez
2002-10-17  2:44                   ` GrandMasterLee
2002-10-17  3:11                     ` Andrew Vasquez
2002-10-17  3:42                       ` GrandMasterLee
2002-10-17  9:40                       ` Michael Clark
2002-10-18  6:45                         ` GrandMasterLee
2002-10-16 16:28       ` Simon Roscic
2002-10-16 16:49         ` Michael Clark
2002-10-17  3:12           ` GrandMasterLee
2002-10-17  3:54             ` Michael Clark
2002-10-17  4:08               ` GrandMasterLee [this message]
2002-10-17  5:03                 ` Michael Clark
2002-10-16  5:02 ` GrandMasterLee
2002-10-16 16:38   ` Simon Roscic
2002-10-17  3:08     ` GrandMasterLee
2002-10-17 17:47       ` Simon Roscic
2002-10-18  6:42         ` GrandMasterLee
2002-10-18 15:11           ` Simon Roscic
  -- strict thread matches above, loose matches on Subject: below --
2002-10-19  2:17 rwhron

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=1034827683.26.76.camel@localhost \
    --to=masterlee@digitalroadkill.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@metaparadigm.com \
    --cc=simon.roscic@chello.at \
    /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.