public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Smart <James.Smart@Emulex.Com>
To: mmzz@stat.unipd.it, linux-scsi@vger.kernel.org
Subject: Re: lp8000 and 2.6.18-rc6
Date: Mon, 11 Sep 2006 08:21:35 -0400	[thread overview]
Message-ID: <450554CF.4060906@emulex.com> (raw)
In-Reply-To: <20060911095109.GA4953@stat.unipd.it>

What this tells me is that the reporting as a scsi-4 device is
telling the midlayer to use Report Luns, and that Report Luns is likely
failing on this target. If the manual scans succeed, it says the
luns are there, but were not reported in Report Luns. What you are
encountering is an interaction between the target device and the midlayer
scan behaviors. You should have like behavior on other adapters.
Sounds like this device could use a device list entry.

Please note: it is general practice that /proc stuff for adapters is
being deprecated in lieu of using the /sys/class/scsi_host/host<#>
attributes. This has been true for the lpfc driver as it was a
requirement when we first integrated into kernel.org around 2.6.10.
Expect other adapters to behave the same as lpfc.

-- james

Alberto Cammozzo wrote:
> On Sun, Sep 10, 2006 at 09:17:30PM -0500, James Bottomley wrote:
>> On Sun, 2006-09-10 at 21:06 -0400, Douglas Gilbert wrote:
>>> Type 0 is for disks, strange that sd didn't pick up
>>> those devices on host 7. Could you fetch the sg3_utils
>>> package, build it and try 'sg_inq /dev/sg6'. The output
>>> may be interesting.
>> That would be characteristic of a zoned array returning PQ not connected
>> (or not present) as James Smart suggested ...
>>
>> sg_inq would confirm this theory.
> 
> 	Thank you James, 
> 
> 	Eventually we managed to solve the problem: 
> 
> 	Debian sarge has an old rescan-scsi-bus.sh version based on /proc
> 	instead of /sys. 
> 
> 	newer lpfc module in 2.6.18 kernels doesn't fill /proc/scsi/HOSTADAPTER, 
> 	so older rescan-scsi-bus don't even try to map new devices.
> 
> 	Summarizing: to make partitions visible with lpfc drivers 
> 	for Emulex LP8000 HBA under 2.6.18 kernels, use newer rescan-scsi-bus 
> 	http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh
> 
> 	Thank you everyone for support and the nice work.
> 
> 	Alberto
> 
> 

  reply	other threads:[~2006-09-11 12:21 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 [this message]
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
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=450554CF.4060906@emulex.com \
    --to=james.smart@emulex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox