linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Mark Lord <kernel@teksavvy.com>
Cc: Al Bogner <suse-linux@ml082.pinguin.uni.cc>, linux-ide@vger.kernel.org
Subject: Re: WDC WD15EARS-00Z5B1: harddrive which does crazy unloading
Date: Thu, 11 Mar 2010 14:53:52 +0900	[thread overview]
Message-ID: <4B988570.4040005@kernel.org> (raw)
In-Reply-To: <4B9881C8.10506@kernel.org>

On 03/11/2010 02:38 PM, Tejun Heo wrote:
> Heh, yeah, that's pretty low.  I hope they eventually learn to adjust
> that dynamically considering running avg of intervals between writes.
> It shouldn't be too hard.

or just bump load cycle limit by x10 or x100.  :-P

storage-fixup can't be the permanent solution.  The only reason I
created it was because I thought it was a passing phase and the
blacklist wouldn't keep growing.

In both reports here, the avg load cycle frequency seems to be about 1
per 2 minutes.  With 300k cycle rating (drives often happily go over
it), it means 1.14 year of continuous operation, which depending on
usage pattern might be considered acceptable.  Maybe the right thing
to do is to simply let it be and if it expires before within the
warranty period, get it RMA'd.

Hmmm... or, we can make a utility which monitors smart output, detects
unload cycle and periodically poll load status and issue a bogus read
whenever the disk unloads its heads so that we can storm the vendors
with RMAs.  :-)

Coming back to the reality, I'll ask vendors about it and see whether
we need to keep worrying about it or we can just let it be.

Thanks.

-- 
tejun

  reply	other threads:[~2010-03-11  5:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08 18:33 WDC WD15EARS-00Z5B1: harddrive which does crazy unloading Al Bogner
2010-03-09  8:05 ` Tejun Heo
2010-03-09  8:13   ` Mikael Abrahamsson
2010-03-09 10:34   ` Al Bogner
2010-03-09 14:40   ` Mark Lord
2010-03-11  5:38     ` Tejun Heo
2010-03-11  5:53       ` Tejun Heo [this message]
2010-03-11 19:10       ` Justin Maggard
2010-03-14 15:57       ` Mark Lord
2010-03-15  0:02         ` Tejun Heo
2010-03-18 16:15           ` Al Bogner
2010-03-18 18:36             ` Justin Maggard
2010-03-19  2:26             ` Tejun Heo
2010-03-19  2:27               ` Tejun Heo
2010-03-23  1:34               ` Mark Lord
     [not found]                 ` <4BA82A2F.7010607@hardwarefreak.com>
2010-03-23  2:44                   ` Stan Hoeppner
2010-04-29 11:00         ` Bjørn Mork

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=4B988570.4040005@kernel.org \
    --to=tj@kernel.org \
    --cc=kernel@teksavvy.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=suse-linux@ml082.pinguin.uni.cc \
    /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).