From: Douglas Gilbert <dougg@torque.net>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Alberto Cammozzo <mmzz@stat.unipd.it>, linux-scsi@vger.kernel.org
Subject: Re: lp8000 and 2.6.18-rc6
Date: Wed, 13 Sep 2006 10:44:06 -0400 [thread overview]
Message-ID: <45081936.4040209@torque.net> (raw)
In-Reply-To: <1158156671.3462.7.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> On Tue, 2006-09-12 at 08:45 +0200, Alberto Cammozzo wrote:
>> novantatre:~# dmesg
>> [...]
>> st 0:0:5:0: Attached scsi generic sg0 type 1
>> ch 0:0:5:1: Attached scsi generic sg1 type 8
>> sd 1:0:0:0: Attached scsi generic sg2 type 0
>> scsi 1:0:15:0: Attached scsi generic sg3 type 3
>> scsi 1:1:9:0: Attached scsi generic sg4 type 3
>> scsi 1:2:8:0: Attached scsi generic sg5 type 3
>> scsi 2:0:0:0: Attached scsi generic sg6 type 0
>> scsi 2:0:1:0: Attached scsi generic sg7 type 0
>> scsi 2:0:2:0: Attached scsi generic sg8 type 0
>> scsi 2:0:3:0: Attached scsi generic sg9 type 0
>
> This shows it found LUNS 0 1 2 3
Wouldn't that be target identifiers 0, 1, 2 and 3
all with luns 0 (the fourth element in the scsi tuple)?
>> sd 3:0:0:0: Attached scsi generic sg10 type 0
>>
>> novantatre:~# sg_luns -v sg6
>> sg_luns: open error: sg6: No such file or directory
>> novantatre:~# sg_luns -v /dev/sg6
>> report luns cdb: a0 00 00 00 00 00 00 00 04 00 00 00
>> report luns: requested 1024 bytes but got 32 bytes
>> Lun list length = 24 which imples 3 lun entries
>>
>> Output response in hex
>> 00 00 00 00 18 00 00 00 00 00 01 00 00 00 00 00 00
>> 10 00 03 00 00 00 00 00 00 00 04 00 00 00 00 00 00
>> Report luns [select_report=0]:
>> 0001000000000000
>> 0003000000000000
>> 0004000000000000
>
> This says the system only has three luns: 1 3 4 (i.e. no 2)
No lun 0 either hence the PQual=1 for the inquiry
response for /dev/sg6 ('sg_inq /dev/sg6'). I suspect
'sg_inq /dev/sg7', sg8 and sg9 also have PQual=1.
There may be a similar pattern to 'sg_luns /dev/sg7',
sg8 and sg9 as was reported for 'sg_luns /dev/sg6'.
> So something really strange is going on here ... The linux code should
> have executed a probe and add luns for the contents of report lun, which
> should have found the correct set, unless something went wrong during
> the reporting.
>
> Can you post the full dmesg from the time the Emulex is detected to the
> time sg attaches? report luns is supposed to issue a failure message if
> something goes wrong (additionally, using the latest -mm would be
> helpful since that prints enhanced inquiry information from scsi-misc).
Yes dmesg would be useful. Is there something stopping
the mid level scanning luns where lun>0 (perhaps something
in the black list)?
Doug Gilbert
next prev parent reply other threads:[~2006-09-13 14:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-09 21:08 lp8000 and 2.6.18-rc6 Alberto Cammozzo
2006-09-10 13:56 ` Matthew Wilcox
2006-09-10 21:04 ` Alberto Cammozzo
2006-09-11 1:06 ` Douglas Gilbert
2006-09-11 2:17 ` James Bottomley
2006-09-11 9:51 ` Alberto Cammozzo
2006-09-11 12:21 ` James Smart
2006-09-11 16:29 ` Alberto Cammozzo
2006-09-11 6:40 ` Alberto Cammozzo
2006-09-11 17:00 ` James Bottomley
2006-09-12 6:45 ` Alberto Cammozzo
2006-09-13 14:11 ` James Bottomley
2006-09-13 14:44 ` Douglas Gilbert [this message]
2006-09-13 15:20 ` James Bottomley
2006-09-13 15:33 ` Patrick Mansfield
2006-09-13 15:37 ` Alberto Cammozzo
-- strict thread matches above, loose matches on Subject: below --
2006-09-09 21:03 Alberto Cammozzo
2006-09-09 21:01 Alberto Cammozzo
2006-09-10 14:03 ` James Smart
2006-09-10 20:43 ` Alberto Cammozzo
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=45081936.4040209@torque.net \
--to=dougg@torque.net \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mmzz@stat.unipd.it \
/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.