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

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

On Fri, Jan 14, 2005 at 10:32:00AM +0100, Guido Guenther wrote:
> On Thu, Jan 13, 2005 at 04:01:15PM -0800, Patrick Mansfield wrote:
> > On Thu, Jan 13, 2005 at 01:40:32PM +0100, Guido Guenther wrote:
> > 
> > > > Can you turn on some scsi logging, and send that?
> > > Sure. I tried scsi_logging_level=... on the kernel command line but it
> > > didn't show anything, did I miss something obvious?
> > > /proc/sys/dev/scsi/logging_level was still zero afterwards.
> > 
> > It is a sysctl variable, so you can set it after you are booted, per my
> > other email (and still below), and man sysctl.
> Yes I saw that, I was just wondering why scsi_logging_level doesn't work
> also it's a module option in scsi.c.

In-kernel module params have to be prefixed by the module name, like:

	scsi_mod.scsi_logging_level=0x2400

AFAIR if the param name is unknown, the kernel outputs a warning.

Note that most (all?) of the other scsi params have the "scsi_" removed,
though the variable name does not, like max_scsi_luns is set via max_luns.

-- Patrick Mansfield