All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Al Bogner <suse-linux@ml082.pinguin.uni.cc>
Cc: Mark Lord <kernel@teksavvy.com>, linux-ide@vger.kernel.org
Subject: Re: WDC WD15EARS-00Z5B1: harddrive which does crazy unloading
Date: Fri, 19 Mar 2010 11:26:48 +0900	[thread overview]
Message-ID: <4BA2E0E8.1050001@kernel.org> (raw)
In-Reply-To: <201003181716.00173.suse-linux@ml082.pinguin.uni.cc>

(cc'ing Daniel, Hi)

Hello,

On 03/19/2010 01:15 AM, Al Bogner wrote:
> WD said to me I can send them the disk, but didn't accept, that this is a 
> firmware bug.
> 
> Today I got a brandnew WD20EARS (2TB) and it is the same. After about an 1/2 
> hr. I had 12 cycles with an _un_formatted disk.

That would reach 1.43 years of operation hour w/ 300k limit.  Maybe
that's the number they are aiming for?  I don't know.  I haven't heard
from WDC yet.

> I cannot accept, that it should be a warranty issue, because this
> reduces the lifetime _after_ the warranty and increases the
> possibility to loose data, at least for those who don't use a raid.
>
> I would be happy to have a native linux utility to change this.

Yeah, that will be nice but it's of very limited use.  How many would
look that up, install it and use it to adjust the parameter?  For it
to have meaningful effect, it should be applied automatically, and at
that point, I'm not sure it's a good idea because I don't want to
unconditionally disable power saving feature without a very good
rationale.

If WDC thinks < 1.5 years of uptime is good enough for those products
in exchange of lowered power consumption, which I think might be
acceptable for certain products considering that most people don't use
their computers 24/7 and the load/unload cycle limit isn't exactly an
accurate timebomb like limit.  Well, then, that's the trade off WDC
made and the consumers can choose accordingly.

And, if that's the case, I think we can and probably should try to let
people know about the particular tradeoff of those drives and if
possible provide a utility to adjust that but I'm still kind of
against automatically disabling it because it doesn't help solving the
situation in the long run while forcing us to apply a sub-optimal
workaround without knowing whether it's really necessary.

Daniel, I think we really need some clarification from WDC at this
point.  I'm sure WDC wouldn't want Linux distros to go ahead and
disable powersaving feature unconditionally, so please let us know.

Thanks.

-- 
tejun

  parent reply	other threads:[~2010-03-19  2:27 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
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 [this message]
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=4BA2E0E8.1050001@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 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.