From: Tejun Heo <htejun@gmail.com>
To: Bruce Allen <ballen@gravity.phys.uwm.edu>
Cc: roland.kletzing@materna.de,
Smartmontools Developers List
<smartmontools-devel@lists.sourceforge.net>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>, Mark Lord <liml@rtr.ca>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
scott@ubuntu.com
Subject: Re: regarding crazy head unloads
Date: Tue, 30 Sep 2008 14:36:16 +0900 [thread overview]
Message-ID: <48E1BAD0.5040608@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0809130635260.26283@gc.phys.uwm.edu>
Bruce Allen wrote:
> Hi Tejun,
>
> Sorry, this is a really really slow reply. This email came at an
> unusually busy time and I did not reply before it got buried in the deluge.
Well, you were slow but I'm slower. :-)
>> 2. This is from Roland. Make smartd aware of the problem and warn user
>> if load/unload count per powered on hours goes too high. Maybe the
>> warning can direct the user to linux-ata.org page?
>
> It would be easy to implement this in smartd. But I'm concerned about
> three things:
>
> -- most people don't run smartd (I think by default it is off on
> the main Linux distros). Those wise enough to run smartd will
> probably be aware of the issue, since it's gotten lots of buzz. And
> even if smartd is turned on in the distro it is normally not
> configured to send warning emails.
We only have to hit one instance of each configuration where such
problem is occurring. I think adding warning message out smartctl
output or letting smartd warn it to users via email or log messages
should be good enough for this problem.
> -- I'm not sure if the attribute used for head load/unload is a standard
> one. On my current laptop Hitachi disk it is attribute 193. Does
> anyone know if this is standard?
I have no idea whatsoever. Maybe implement a regexp matching on
attribute name?
> -- I'm not sure at what threshold to send warning emails. If we send
> too many false alarms, they will be ignored by users.
To get it correct completely, I think we'll need per-device database.
Not easy.... :-(
Thanks.
--
tejun
prev parent reply other threads:[~2008-09-30 5:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 1:36 regarding crazy head unloads Tejun Heo
2008-05-23 11:36 ` Tejun Heo
2008-06-02 9:55 ` Scott James Remnant
2008-06-09 1:56 ` Tejun Heo
2008-09-13 11:44 ` Bruce Allen
2008-09-30 5:36 ` Tejun Heo [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=48E1BAD0.5040608@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ballen@gravity.phys.uwm.edu \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=roland.kletzing@materna.de \
--cc=scott@ubuntu.com \
--cc=smartmontools-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.