Re: [PATCH] REPORT LUN scan even if no storage is available on LUN 0

[Patrick Mansfield <patmans@us.ibm.com>]

On Mon, Jan 10, 2005 at 05:42:00PM +0100, Guido Guenther wrote:
> Sorry it took me so long to test this, first time I'm near this hardware
> again.
> On Mon, Dec 13, 2004 at 02:22:06PM -0800, Patrick Mansfield wrote:
> > Patch looks okay, but we should always be trying the report lun scan, and
> > then failing back to the sequential scan even if there is no storage on
> > LUN 0.
> 
> > Can you test this? I don't have hardware readily available that supports
> > sparse luns and report lun. Patch is against current bk. I built and
> > ran with regular disks (lun 0 only).
> Doesn't work here. I doen't see any devices in /proc/scsi/scsi now.
>  -- Guido

So it worked some without the patch (I think you only saw some of the LUNs
before)?

What is output during the scan?

Can you turn on some scsi logging, and send that?

If you have root on scsi, you should shutdown syslogd (though this should
not generate lots of logging for small amounts of IO it generates some,
and if you screw up you'll be able to disable the logging), and then 
capture the console/serial output.

If root on ide, just leave syslog on and get /var/log/messages output.

Turn on per-command and scan logging (0x2400 | 0x01c0):

	sysctl -w dev.scsi.logging_level=0x25c0

Set back off afterwards with:

	sysctl -w dev.scsi.logging_level=0

-- Patrick Mansfield