public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: GrandMasterLee <masterlee@digitalroadkill.net>
To: Michael Clark <michael@metaparadigm.com>
Cc: jbradford@dial.pipex.com, linux-kernel@vger.kernel.org
Subject: Re: QLogic Linux failover/Load Balancing ER0000000020860
Date: 07 Oct 2002 00:24:02 -0500	[thread overview]
Message-ID: <1033968242.3948.1.camel@localhost> (raw)
In-Reply-To: <3DA11884.7050004@metaparadigm.com>

On Mon, 2002-10-07 at 00:15, Michael Clark wrote:

> So sparse lun scanning is working then - sounds like your missing luns
> is a problem with your array configuration as the kernel is probing them
> (if it is was creating the even ones) - means the qlogic driver must
> not be able to see these luns. Not familiar with your array so can't
> help any more - your array vendor would probably be the most help.
> 
> ~mc
> 

Seems so. The odd thing is, that the hba1, vs. hba0, is not listed as
seeing any LUNs just existing. I'll go back and re-check my config. My
DSL really sux ATM, so doing things through X sessions has been a bit
painful. 

--The GrandMaster

  reply	other threads:[~2002-10-07  5:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <41EBA11203419D4CA8EB4C6140D8B4017CD8EE@AVEXCH01.qlogic.org>
2002-10-06  0:09 ` QLogic Linux failover/Load Balancing ER0000000020860 Austin Gonyou
2002-10-06  3:18   ` GrandMasterLee
2002-10-06 10:19     ` jbradford
2002-10-06 10:31       ` GrandMasterLee
2002-10-06 11:03         ` jbradford
2002-10-06 12:26           ` Michael Clark
2002-10-06 19:40             ` GrandMasterLee
2002-10-06 23:14               ` GrandMasterLee
2002-10-07  4:54                 ` GrandMasterLee
2002-10-07  5:15                   ` Michael Clark
2002-10-07  5:24                     ` GrandMasterLee [this message]
2002-10-06  7:58   ` Lars Marowsky-Bree
2002-10-07 16:32     ` Austin Gonyou
2002-10-06 15:45 James Bottomley
2002-10-06 19:46 ` GrandMasterLee

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=1033968242.3948.1.camel@localhost \
    --to=masterlee@digitalroadkill.net \
    --cc=jbradford@dial.pipex.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