public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: GrandMasterLee <masterlee@digitalroadkill.net>
To: linux-kernel@vger.kernel.org
Subject: RE: QLogic Linux failover/Load Balancing ER0000000020860
Date: 05 Oct 2002 22:18:45 -0500	[thread overview]
Message-ID: <1033874298.4209.5.camel@localhost> (raw)
In-Reply-To: <1033862965.27451.51.camel@UberGeek.coremetrics.com>

I was hoping someone on this list might have some ideas about this.
Please respond to me at this address or the Coremetrics one.  I'm not
sure exactly what approach to take on this. Any hints would be helpful.


TIA.

On Sat, 2002-10-05 at 19:09, Austin Gonyou wrote:
> The latest driver does not load balance with STK D178 array either.
> 
> I've discovered why, but I'm not sure which direction to take with
> helping out to get better closure/resolution with this.
> 
> 
> The cause of the problem is that the QLogic driver doesn't to
> transparent LUN masking it seems. The reason this is a problem, is that
> when the LSI/StoragTEK controllers present their luns, AVT is enabled.
> This causes LUN "ghosting" down each path from the storage to the HBAs.
> This becomes a problem because when the Linux Driver is told to perform
> load balancing via static bindings, the LUNs are now out of order.
> (whether LUN ghosting is happening or not). 
> 
....
> Linux is not allowed to address LUNs out of sequence, so searching for
> further LUN numbers stops after 0, since 2 is the next one. 
> 
> Is there a way to resolve this, either at the driver level, IMHO the
> place it *should* happen. At the storage level, the place that it could
> also happen, or in the Kernel?
> 
> For the time being, I'm using a temporary load balanced setup for
> performance reasons since we just extended our two primary loops from 1
> tray each, to 3 and 4 trays. Please advise ASAP, as in this
> configuration, we cannot fail-over. 
> 
> TIA
> -- 
> Austin Gonyou <austin@coremetrics.com>
> Systems Architect
> Coremetrics, Inc.
> Cel: 512-698-7250
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2002-10-06  3:13 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 [this message]
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
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=1033874298.4209.5.camel@localhost \
    --to=masterlee@digitalroadkill.net \
    --cc=linux-kernel@vger.kernel.org \
    /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