From: Pete Zaitcev <zaitcev@redhat.com>
To: dledford@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: scsi_scan problem.
Date: Wed, 14 Mar 2001 21:35:43 -0500 [thread overview]
Message-ID: <20010314213543.A30816@devserv.devel.redhat.com> (raw)
In-Reply-To: <3AB028BE.E8940EE6@redhat.com>
In-Reply-To: <3AB028BE.E8940EE6@redhat.com>; from dledford@redhat.com on Wed, Mar 14, 2001 at 09:28:14PM -0500
> Date: Wed, 14 Mar 2001 21:28:14 -0500
> From: Doug Ledford <dledford@redhat.com>
> A bug report I was charged with fixing (qla2x00 driver doesn't see all luns or
> sees multiple identical luns in different scenarios) was not a bug in the
> qla2x00 driver. [...]
> The bug is that we were detecting offline devices and linking
> them into the device list.
Why is this a bug? What would happen when I telnet into the
the RAID box and enable my volumes on those LUNs?
> But, some devices (at least the Clariion raid
> chassis) report luns that don't currently have any device bound to them as
> present but offline. This meant if we truly scanned all luns then we got
> something like 100+ devices on one ID from this chassis when only 1 might be
> valid:-(
16384 LUNs for Fibre Channel. As you see, scanning is out of the
question. You must issue REPORT LUNs and fall back on scanning
if the device reports a check condition. I did that when I worked
in Sun Storage with A5000/A3500/T3 arrays couple of years ago.
-- Pete
next prev parent reply other threads:[~2001-03-15 2:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 2:28 scsi_scan problem Doug Ledford
2001-03-15 2:35 ` Pete Zaitcev [this message]
2001-03-15 3:03 ` Doug Ledford
2001-03-15 3:09 ` Doug Ledford
2001-03-16 16:53 ` Ishikawa
2001-03-16 19:33 ` Doug Ledford
2001-03-16 20:10 ` Peter Rival
2001-03-17 2:08 ` Ishikawa
2001-03-15 5:06 ` Bob Frey
2001-03-15 5:19 ` Doug Ledford
2001-03-16 22:39 ` Rafael E. Herrera
2001-03-16 22:54 ` Doug Ledford
2001-03-16 23:40 ` Khalid Aziz
2001-03-17 0:12 ` Patrick Mansfield
2001-03-17 1:56 ` Doug Ledford
2001-03-17 3:37 ` Rafael E. Herrera
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=20010314213543.A30816@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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