From: Jeff Moyer <jmoyer@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: linux-scsi@vger.kernel.org, David Zeuthen <david@fubar.dk>
Subject: Re: scsi error handler thread seems to run continuously
Date: Fri, 28 May 2010 19:30:21 -0400 [thread overview]
Message-ID: <x49hblrbo4y.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <AANLkTim-dZFhUm8IOLwQhNLovBmUxb5AnGYmbYci1YYK@mail.gmail.com> (Mike Snitzer's message of "Fri, 28 May 2010 17:55:32 -0400")
Mike Snitzer <snitzer@redhat.com> writes:
> Chatting with James on #storage we arrived at the fact that in my case
> the error handler was being triggered by: hald-addon-storage: polling
> /dev/sr0 (every 16 sec)
>
> Killing hald-addon-storage stops the 16s periodic scsi error handler messages.
Ahh, silence. On my system, hald-addon-storage was polling /dev/sr0
every 2 seconds. Killing this process, there's now nothing going on.
Thanks a ton!
-Jeff
prev parent reply other threads:[~2010-05-28 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 21:07 scsi error handler thread seems to run continuously Jeff Moyer
2010-05-28 21:55 ` Mike Snitzer
2010-05-28 23:30 ` Jeff Moyer [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=x49hblrbo4y.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=david@fubar.dk \
--cc=linux-scsi@vger.kernel.org \
--cc=snitzer@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;
as well as URLs for NNTP newsgroup(s).