From: "Christian Pernegger" <pernegger@gmail.com>
To: "Helge Hafting" <helge.hafting@aitel.hist.no>
Cc: "Tvrtko A. Ursulin" <tvrtko@ursulin.net>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Western Digital GreenPower drives and Linux
Date: Wed, 16 Apr 2008 19:59:24 +0200 [thread overview]
Message-ID: <bb145bd20804161059u4fe45debs22adf337fef143aa@mail.gmail.com> (raw)
In-Reply-To: <4805E59E.1020607@aitel.hist.no>
> > At this rate the disk would reach it's design limit for load/unload cycles
> in around 80 days.
Design *minimum* for load/unload cycles is reportedly 600K cycles,
that would give me over 7.5 years of 24/7 operation, which I can live
with in cheap high capacity drives that have only 5 years of warranty
anyway.
Support wouldn't say if the behavior is considered normal, though ...
Will set the timeout to 25sec using the DOS kludge and see what
happens ... doubt it will help much, though. I'd much rather like to
know what causes the drives to load heads again so soon after the
unload. With the usage pattern of these drives they should stay
unloaded most of the time here.
Being able to set the timeout online via hdparm would be nice, too :)
C.
next prev parent reply other threads:[~2008-04-16 17:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 20:18 Tvrtko A. Ursulin
2008-04-10 7:48 ` 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 [this message]
2008-04-16 18:18 ` Mark Lord
2008-04-16 19:44 ` Tvrtko A. Ursulin
2008-04-16 19:46 ` Tvrtko A. Ursulin
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
2008-04-27 17:45 devzero
2008-04-27 19:14 ` Renato S. Yamane
2008-04-29 15:22 ` 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=bb145bd20804161059u4fe45debs22adf337fef143aa@mail.gmail.com \
--to=pernegger@gmail.com \
--cc=helge.hafting@aitel.hist.no \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tvrtko@ursulin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome