From: Stanislaw Gruszka <stf_xl@wp.pl>
To: linux-kernel@vger.kernel.org
Subject: Implementing events about block layer errors?
Date: Thu, 7 Feb 2008 10:19:22 +0100 [thread overview]
Message-ID: <200802071019.22632.stf_xl@wp.pl> (raw)
Hello.
My boss wants me to add disk errors uevents, to get information on faulty
devices. He told me catching dmesg information using syslog is not reliable
and he would like to get 100% certain information. I know there are currently
implemented uevents in the device mapper layer, but they are limited to
multipath targets. Even if error events were added to the device mapper,
would it be impossible to find out which physical device generates errors
if the device mapper works on top of the software RAID (correct?).
Does it make sense to add such a functionality to the block layer
(or somewhere else), and also could such a modification be included
in the mainline kernel, or should I rather convince my boss to implement
it via syslog?
Stanislaw Gruszka
reply other threads:[~2008-02-07 9:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200802071019.22632.stf_xl@wp.pl \
--to=stf_xl@wp.pl \
--cc=linux-kernel@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