From: Patrick Mansfield <patmans@us.ibm.com>
To: Guido Guenther <agx@sigxcpu.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] REPORT LUN scan even if no storage is available on LUN 0
Date: Fri, 14 Jan 2005 08:51:42 -0800 [thread overview]
Message-ID: <20050114165142.GA32650@us.ibm.com> (raw)
In-Reply-To: <20050114132623.GA7837@bogon.ms20.nix>
On Fri, Jan 14, 2005 at 02:26:23PM +0100, Guido Guenther wrote:
> On Thu, Jan 13, 2005 at 04:21:34PM -0800, Patrick Mansfield wrote:
> This is the target that has all the devices:
> # echo "0 0 -" > /sys/class/scsi_host/host0/scan
> scsi_scan_host_selected: <0:0:0:4294967295>
> scsi scan: INQUIRY to host 0 channel 0 id 0 lun 0
> scsi <0:0:0:0> send scsi0 : destination target 0, lun 0
> command = Inquiry 00 00 00 24 00
> scsi <0:0:0:0> done SUCCESS 0 scsi0 : destination target 0, lun 0
> command = Inquiry 00 00 00 24 00
> scsi scan: 1st INQUIRY successful with code 0x0
> scsi <0:0:0:0> send scsi0 : destination target 0, lun 0
> command = Inquiry 00 00 00 95 00
> scsi <0:0:0:0> done SUCCESS 0 scsi0 : destination target 0, lun 0
> command = Inquiry 00 00 00 95 00
> scsi scan: 2nd INQUIRY successful with code 0x0
> scsi scan: peripheral qualifier of 3, no device added
> scsi scan: Sequential scan of host 0 channel 0 id 0
>
> While this is an empty one:
> # echo "0 1 -" > /sys/class/scsi_host/host0/scan
> scsi_scan_host_selected: <0:0:1:4294967295>
> scsi scan: INQUIRY to host 0 channel 0 id 1 lun 0
> scsi <0:0:1:0> send scsi0 : destination target 1, lun 0
> command = Inquiry 00 00 00 24 00
> scsi <0:0:1:0> done SUCCESS 10000 scsi0 : destination target 1, lun 0
> command = Inquiry 00 00 00 24 00
> scsi scan: 1st INQUIRY failed with code 0x10000
Your device must be reporting as SCSI-2, that makes sense, since you
needed other bflags set. The logging should really dump the scsi_level.
You need to add an entry to the devinfo list to force a REPORT LUNs scan.
I don't know why it is not already in scsi_devinfo.c, AFAIR REPORT LUNs
has always worked with EMC, and should be in its devinfo flag (and
probably the only devinfo flag, since sparse, largelun and forcelun are
meaningless for a REPORT LUN scan).
module params can be used, but /proc/scsi/device_info is easiest. Make
sure I have the correct vendor:model, this should work:
echo "EMC:SYMMETRIX:0x20000" > /proc/scsi/device_info
BLIST_REPORTLUN2 is 0x20000.
-- Patrick Mansfield
prev parent reply other threads:[~2005-01-14 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 12:33 RFC/patch: bflags not applied in case of SCSI_SCAN_TARGET_PRESENT Guido Guenther
2004-12-13 22:22 ` [PATCH] REPORT LUN scan even if no storage is available on LUN 0 Patrick Mansfield
2005-01-10 16:42 ` Guido Guenther
2005-01-11 18:15 ` Patrick Mansfield
2005-01-13 12:40 ` Guido Guenther
2005-01-14 0:01 ` Patrick Mansfield
2005-01-14 9:32 ` Guido Guenther
2005-01-14 16:28 ` Patrick Mansfield
2005-01-14 0:21 ` Patrick Mansfield
2005-01-14 13:26 ` Guido Guenther
2005-01-14 16:51 ` Patrick Mansfield [this message]
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=20050114165142.GA32650@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=agx@sigxcpu.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 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.