All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Clark <michael@metaparadigm.com>
To: GrandMasterLee <masterlee@digitalroadkill.net>
Cc: J Sloan <joe@tmsusa.com>, Simon Roscic <simon.roscic@chello.at>,
	Arjan van de Ven <arjanv@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [Kernel 2.5] Qlogic 2x00 driver
Date: Wed, 16 Oct 2002 14:40:35 +0800	[thread overview]
Message-ID: <3DAD09E3.2050602@metaparadigm.com> (raw)
In-Reply-To: 1034749907.2045.15.camel@localhost

On 10/16/02 14:31, GrandMasterLee wrote:
> On Wed, 2002-10-16 at 01:03, Michael Clark wrote:
> 
>>On 10/16/02 12:43, GrandMasterLee wrote:
>>
[snip]
>>>All hardware configuration bits are perfect, as can be anyway, and we
>>>still get this behaviour. After 5-6.5 days...the box black screens. So
>>>bad so, that all the XFS volumes we have, never enter a shutdown. We
>>>must repair them all, today this happened, and we lost one part of the
>>>tablespace on our beta db. We're using LVM1, on 2.4.19-aa1.
>>
>>We had the black screen also until we got the machines oopsing over
>>serial. The oops was actually showing up in ext3 with a corrupted
>>bufferhead. Without LVM, i've measured my longest uptime, 17 days x
>>4 machines in the cluster (68 days) ie. we only did it 17 days ago.
> 
> I believe you, that was my next thought, but I didn't know if that would
> really help just to be honest. Thanks for the input there. 
> 
> I've been going crazy trying to catch any piece of sanity out of this
> thing to understand if this was what was happening or not. I feel a bit
> dumb for not trying serial console yet, but I knew either that or KDB
> should tell us something. I will see what we can do, it will take less
> time to do this, than to reload everything all over again.
> 
> Should I remove LVM all together, or just not use it? In your opinion.

I just didn't load the module after migrating my volumes. If the problem
is a stack problem, then its probably not necessarily a bug in LVM
- just the combination of it, ext3 and the qlogic driver don't mix well
- so if its not being used, then it won't be increasing the stack footprint.

~mc


  reply	other threads:[~2002-10-16  6:34 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 [this message]
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
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=3DAD09E3.2050602@metaparadigm.com \
    --to=michael@metaparadigm.com \
    --cc=arjanv@redhat.com \
    --cc=joe@tmsusa.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masterlee@digitalroadkill.net \
    --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.