From: Matthew Wilcox <matthew@wil.cx>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: James Smart <James.Smart@Emulex.Com>,
Eddie Williams <Eddie.Williams@steeleye.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Print SCSI Inquiry data more compactly
Date: Wed, 21 Jun 2006 13:03:27 -0600 [thread overview]
Message-ID: <20060621190327.GB1630@parisc-linux.org> (raw)
In-Reply-To: <44998A34.20202@s5r6.in-berlin.de>
On Wed, Jun 21, 2006 at 08:04:36PM +0200, Stefan Richter wrote:
> Matthew Wilcox wrote:
> >On Wed, Jun 21, 2006 at 01:18:43PM -0400, James Smart wrote:
> >>scsi <2:0:1:0> x00:HP 18.2G:ATLAS10K3_18_SCA:HP05:02:
> >>Eddie Williams wrote:
> >>>scsi 2:0:1:0:DASD:HP 18.2G:ATLAS10K3_18_SCA:HP05:02:
> >scsi 2:0:1:0: Direct-Access HP 18.2G ATLAS10K3_18_SCA HP05 ANSI ver:
> >01 CCS
> >scsi 2:0:1:0: Direct-Access xAB HP 18.2G ATLAS10K3_18_SCA HP05 Level:
> >03
> >scsi 2:0:1:0: Direct-Access 7 HP 18.2G ATLAS10K3_18_SCA HP05 Level: 03
>
> All of these hurt eyes. What is wrong with the current two-line format?
Several things. The way that it's printed means that simultaneous scans
lead to the output getting garbled. Also, when doing simultaneous scans,
it's no longer clear (was it ever?) which device a particular scan message
belongs to. That argues for attaching the scsi bus ID to the printk, and
making it all one line, and as atomic as possible. James tells me that
having the PQ number included helps determine problems with multipathing.
> One line too many? What about silencing protocol drivers first? sd puts
> out a lot of lines right after those inquiry data. What's more, sd is
> forced by some upper layer to go through the initialization twice,
> therefore sd sees fit to print its stuff out twice. This is where I see
> potential to reduce log noise.
There's a lot of places SCSI is too verbose. I intend to address all of
them eventually; having hundreds of SCSI devices is really no fun right
now. That cause isn't helped by people placing spurious roadblocks in
the way.
> Highly cryptic log messages on the other hand are about as valuable as
> _no_ log messages at all. The lines I quoted above are not far from
> white noise.
You're exaggerating. BTW, here's what a line would look like from sbp2 ...
scsi 9:0:0:0: CD-ROM MATSHITA UJDA730 DVD/CDRW 1.00 Level: 0
btw, I've always found that "CD-ROM" a little confusing; considering
that SPC4 says "CD/DVD device", any objections to changing that string
to say "CD/DVD" instead of "CD-ROM"?
next prev parent reply other threads:[~2006-06-21 19:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 15:42 [PATCH] Print SCSI Inquiry data more compactly Salyzyn, Mark
2006-06-21 16:41 ` Philip R. Auld
2006-06-21 16:50 ` Matthew Wilcox
2006-06-21 17:02 ` Eddie Williams
2006-06-21 17:18 ` James Smart
2006-06-21 17:33 ` Matthew Wilcox
2006-06-21 18:04 ` Stefan Richter
2006-06-21 19:03 ` Matthew Wilcox [this message]
2006-06-21 22:36 ` Stefan Richter
2006-06-22 2:55 ` Douglas Gilbert
2006-06-21 17:47 ` Philip R. Auld
2006-06-21 22:14 ` Stefan Richter
2006-06-21 22:23 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2006-06-20 22:27 Matthew Wilcox
2006-06-21 14:50 ` Douglas Gilbert
2006-06-21 15:47 ` Matthew Wilcox
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=20060621190327.GB1630@parisc-linux.org \
--to=matthew@wil.cx \
--cc=Eddie.Williams@steeleye.com \
--cc=James.Smart@Emulex.Com \
--cc=linux-scsi@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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.