From: Johannes Truschnigg <johannes@truschnigg.info>
To: Mark Knecht <markknecht@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: mdadm: sending ioctl 800c0910 to a partition!
Date: Wed, 18 Apr 2012 10:21:21 +0200 [thread overview]
Message-ID: <20120418082121.GA6690@vault.local> (raw)
In-Reply-To: <CAK2H+efFUYqX98KBSdJAu-wH5c+Aec2+1K40uQVostDgyh8PYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]
On Tue, Apr 17, 2012 at 08:48:06PM -0700, Mark Knecht wrote:
> Wondering if I should be concerned about these new messages?
>
> [...]
Not a reason for concern; this was introduced into the kernel to detect (and
then hopefully fix) misbehaving userspace, afaik. Having these messages in the
debug ringbuffer is annyoing for sure, but seeing it make its way into your
syslog is what really drove me a bit mad (esp. as Proxmox seems to poll block
devices in a weird way, which generated such messages at a rate of several
dozen entries per minute...).
I made rsyslog (on Debian Squeeze) discard the kind of message by introducing
a regex filter to its chain of rules by creating a file
"/etc/rsyslog.d/zz-local.conf" with the following lines as its content:
:msg, regex, ".*sending ioctl [0-9][0-9]* to a partition.*" ~
:msg, regex, ".*scsi_verify_blk_ioctl: [0-9][0-9]* callbacks suppressed.*" ~
Maybe that's helpful for someone who doesn't like getting their logs spammed
with pretty meaningless noise, too.
--
with best regards:
- Johannes Truschnigg ( johannes@truschnigg.info )
www: http://johannes.truschnigg.info/
phone: +43 650 2 133337
xmpp: johannes@truschnigg.info
Please do not bother me with HTML-email or attachments. Thank you.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-04-18 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 3:48 mdadm: sending ioctl 800c0910 to a partition! Mark Knecht
2012-04-18 4:34 ` Jack Wang
2012-04-18 8:21 ` Johannes Truschnigg [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=20120418082121.GA6690@vault.local \
--to=johannes@truschnigg.info \
--cc=linux-raid@vger.kernel.org \
--cc=markknecht@gmail.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;
as well as URLs for NNTP newsgroup(s).