From: Junliang Li <lijunliang.dna@gmail.com>
To: hare@suse.de
Cc: linux-scsi@vger.kernel.org
Subject: Can we use SCSI error trace events to monitor SCSI hardware problems ?
Date: Mon, 23 Dec 2013 11:28:23 +0800 [thread overview]
Message-ID: <1387769303.2695.20.camel@localhost> (raw)
Hello, Hannes
I found you owned a project on github named "md_monitor". It supports MD
array by using mdadm tool. But how about generic SCSI devices ? There is
a "scsi_dispatch_cmd_error" tracepoint in SCSI subsystem, from which we
can get something useful output via sysfs. We can do more work in
userspace. Now I setup a tracepoint in "scsi_print_result" and trace
scsi cmd result. By reading host status and sense data, I can find out
anything wrong while executing SCSI commands. Does it make sense or it
could be better ?
Thanks,
Junliang Li
next reply other threads:[~2013-12-23 3:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 3:28 Junliang Li [this message]
2014-01-02 14:51 ` Can we use SCSI error trace events to monitor SCSI hardware problems ? Hannes Reinecke
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=1387769303.2695.20.camel@localhost \
--to=lijunliang.dna@gmail.com \
--cc=hare@suse.de \
--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).