From: jbradford@dial.pipex.com
Message-Id: <200210061019.g96AJ9KA001206@darkstar.example.net>
Subject: Re: QLogic Linux failover/Load Balancing ER0000000020860
To: masterlee@digitalroadkill.net (GrandMasterLee)
Date: Sun, 6 Oct 2002 11:19:09 +0100 (BST)
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <1033874298.4209.5.camel@localhost> from "GrandMasterLee" at Oct 05, 2002 10:18:45 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 923
Lines: 23

> > 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. 

That's not true:

CONFIG_SCSI_REPORT_LUNS:

If you want to build with SCSI REPORT LUNS support i the kernel, say Y here.
The REPORT LUNS command is useful for devices (such as disk arrays) with large numbers of LUNs where the LUN values are not contiguous (sparse LUN).
REPORT LUNS scanning is done only for SCSI-3 devices.

> > 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?

This is new in 2.5.x

John.
-
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/