linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tvrtko A. Ursulin" <tvrtko@ursulin.net>
To: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Western Digital GreenPower drives and Linux
Date: Wed, 9 Apr 2008 21:18:35 +0100	[thread overview]
Message-ID: <200804092118.35501.tvrtko@ursulin.net> (raw)


Hi all,

The subject may be a bit misleading since I haven't investigated the whole 
issue under other OS-es (nor do I plan to), but this is how the story goes..

Those fancy new WD GreenPower drives seem to be heavily suffering from the 
rapidly increasing head load/unload problem. And the bad thing is they don't 
respond to 'hdparm -B', which would mean (I think) their power management 
behaviour is solely up to their firmware.

I got one of them (WD5000AACS) recently and to my horror after less than three 
days of being power on this is what I saw:

9 Power_On_Hours       0x0032 100 100 000 Old_age Always  - 66
193 Load_Cycle_Count 0x0032 197 197 000 Old_age  Always  - 10233

At this rate the disk would reach it's design limit for load/unload cycles in 
around 80 days. Not good - so I implemented a lame workaround of keeping disk 
busy every couple of seconds - hopefully that won't kill it sooner that 
unloads would..

I am also currently talking with first line of WD's tech support trying to get 
some data on how exactly those drives manage head unloading, but that may not 
lead anywhere useful.

So in parallel I decided to ask here to see if someone knows something about 
this?

If it matters, I am running vanilla 2.6.24 on that box and sata_sil is driving 
that disk. Otherwise it is a pretty basic Ubuntu 7.10, a mix of ext3 and jfs 
filesystems, all mounted with noatime. More detailed information available on 
request.

Tvrtko





             reply	other threads:[~2008-04-09 20:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09 20:18 Tvrtko A. Ursulin [this message]
2008-04-10  7:48 ` Western Digital GreenPower drives and Linux Tvrtko A. Ursulin
2008-04-10 12:44   ` Kasper Sandberg
2008-04-10 15:01     ` Christian Pernegger
2008-04-12 17:11       ` Jan Engelhardt
2008-04-13 15:41         ` Mark Lord
2008-04-16 11:40 ` Helge Hafting
2008-04-16 17:59   ` Christian Pernegger
2008-04-16 18:18     ` Mark Lord
2008-04-16 19:44     ` Tvrtko A. Ursulin
2008-04-16 19:46   ` Tvrtko A. Ursulin
  -- strict thread matches above, loose matches on Subject: below --
2008-04-10 22:36 devzero
2008-04-11 21:00 ` Tvrtko A. Ursulin
2008-04-12  3:19   ` Mike Snitzer
2008-04-12  7:11     ` Tvrtko A. Ursulin
2008-04-12 15:20       ` Mike Snitzer
2008-04-12 15:56         ` Mike Snitzer
2008-04-13  8:30           ` Niels

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=200804092118.35501.tvrtko@ursulin.net \
    --to=tvrtko@ursulin.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).