linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 13 Jan 2005 16:01:15 -0800	[thread overview]
Message-ID: <20050114000115.GA13676@us.ibm.com> (raw)
In-Reply-To: <20050113124032.GB5701@bogon.ms20.nix>

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.

If you are building the qlogic driver into the kernel you can still rescan
the LUNs via:

	echo "- - -" > /sys/class/scsi_host/hostN/scan

> > 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

  reply	other threads:[~2005-01-14  0:01 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 [this message]
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

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=20050114000115.GA13676@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).