From: Martin Wilck <mwilck@suse.de>
To: mgandhi@redhat.com, Laurence Oberman <loberman@redhat.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Cc: jejb@linux.ibm.com, martin.petersen@oracle.com
Subject: Re: [PATCH] scsi: core: Log SCSI command age with errors
Date: Mon, 30 Sep 2019 11:46:06 +0200 [thread overview]
Message-ID: <c0f30c298cd40dc3dee8d6963f60f72330e7de72.camel@suse.de> (raw)
In-Reply-To: <31eb5bb6-ca4e-1c6c-3013-7d94ff49623d@redhat.com>
Hello Milan,
On Mon, 2019-09-30 at 14:35 +0530, Milan P. Gandhi wrote:
> On 9/30/19 2:12 PM, Martin Wilck wrote:
> > Wrt the enablement of the option on highly loaded systems, I'm not
> > sure
> > I understand. You need to enable SCSI logging anyway, don't you?
>
> By default we keep the SCSI debug logging disabled or am I missing
> something?
>
> > Is it an issue to have to set 2 sysfs values rather than just one?
>
> The idea here is to capture the above debug data even without
> any user interventions to change any sysfs entries or to enable
> debug logging on busy, critical production systems.
So, you're looking at the scsi_io_completion() code path. In my
experience that isn't reliable for bug hunting because of the the
message rate limiting. Therefore I prefer using SCSI logging
MLCOMPLETE=1, where no rate limiting applies. But that's just a side
note, it depends on the case what's more useful.
Back to the cmd age output, IMO we're are on a thin line between
capturing useful information and keeping the logs neat. As I already
said, I'm not convinced that this information, as important it may be
for the case(s) you're currently investigating, has the same generic
degree of importance or usefulness as what's currently printed (the CDB
and the sense data). But OTOH, that's just a gut feeling, and I can't
claim to have the experience to make general statement on it. If noone
else has issues with this being printed by default, I'm not going
oppose it.
> Also, we are not changing the existing text in SCSI command error
> log,
> but we are only adding one single word at the end of message. Ideally
> the user scripts are written to grep specific pattern from the logs.
> Since we are not replacing any existing text from the logs, the
> scripts should still work with this change as well.
You are certainly aware that such scripts don't necessarily conform to
what kernel developers would consider "ideal" :-) But again, I just
wanted to raise the issue; if noone else thinks it matters, fine with
me.
Thanks
Martin
prev parent reply other threads:[~2019-09-30 9:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 6:01 Milan P. Gandhi
2019-09-23 13:02 ` Laurence Oberman
2019-09-23 13:24 ` Milan P. Gandhi
2019-09-25 15:45 ` Bart Van Assche
2019-09-26 5:01 ` Milan P. Gandhi
2019-09-27 15:26 ` Martin Wilck
2019-09-27 17:45 ` Laurence Oberman
2019-09-30 8:42 ` Martin Wilck
2019-09-30 9:05 ` Milan P. Gandhi
2019-09-30 9:46 ` Martin Wilck [this message]
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=c0f30c298cd40dc3dee8d6963f60f72330e7de72.camel@suse.de \
--to=mwilck@suse.de \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=martin.petersen@oracle.com \
--cc=mgandhi@redhat.com \
/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
all inboxes | Powered by JetHome®