linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Elias Oltmanns <eo@nebensachen.de>
Cc: raz ben yehuda <razb@bitband.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH 4/4 v2] Add documentation for hard disk shockprotection interface
Date: Sat, 20 Sep 2008 19:25:09 -0400	[thread overview]
Message-ID: <48D58655.5060300@kernel.org> (raw)
In-Reply-To: <87ej3f7pwr.fsf@denkblock.local>

Hello,

Elias Oltmanns wrote:
> Disk head parking is meant as a short term emergency resort. In general,
> it does *not* extend the lifetime of a disk. In fact, emergency head
> unloads are considered to be costly and smart even counts those events
> as an aging factor. It really is just a means to prevent even worse
> damage due to heavy shocks, nothing for regular maintenance.

Just slight clarification.  Emergency head unload has nothing much to
do with explicit head unload used for shock protection.  Emergency
head unload happens when the power is lost while the head is loaded,
that is, when the power is turned off without preceding IDLE IMMEDIATE
or STANDBYNOW.  But other than that, AFAIK, Elias's statement is
correct.  It's unclear whether unloading the head or spinning down the
drive would extend or shorten the lifetime of a disk.

-- 
tejun

      reply	other threads:[~2008-09-20 23:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17 16:28 Disk shock protection in GNU/Linux Elias Oltmanns
2008-09-17 16:34 ` [PATCH 1/4 v2] Introduce ata_id_has_unload() Elias Oltmanns
2008-09-17 16:57   ` Tejun Heo
2008-09-18 23:24     ` Bartlomiej Zolnierkiewicz
2008-09-17 16:37 ` [PATCH 2/4 v2] libata: Implement disk shock protection support Elias Oltmanns
2008-09-17 18:03   ` Tejun Heo
2008-09-17 18:08   ` Tejun Heo
2008-09-17 18:09   ` Tejun Heo
2008-09-19  9:49     ` Elias Oltmanns
2008-09-19 12:14       ` Tejun Heo
2008-09-19 14:06         ` Elias Oltmanns
2008-09-19 14:15           ` Tejun Heo
2008-09-19 15:00             ` Elias Oltmanns
2008-09-20  4:48               ` Tejun Heo
2008-09-17 16:38 ` [PATCH 3/4 v2] ide: " Elias Oltmanns
2008-09-18 23:24   ` Bartlomiej Zolnierkiewicz
2008-09-19  0:28     ` Elias Oltmanns
2008-09-19  0:47       ` Bartlomiej Zolnierkiewicz
2008-10-04  9:44     ` Elias Oltmanns
2008-10-04 13:49       ` Elias Oltmanns
2008-10-04 23:16         ` Elias Oltmanns
2008-10-08 18:56           ` Bartlomiej Zolnierkiewicz
2008-09-17 16:40 ` [PATCH 4/4 v2] Add documentation for hard disk shock protection interface Elias Oltmanns
2008-09-18 23:28   ` Bartlomiej Zolnierkiewicz
2008-10-04  9:55     ` Elias Oltmanns
2008-10-08 18:56       ` Bartlomiej Zolnierkiewicz
2008-09-19  4:21   ` Grant Grundler
2008-09-19 12:08     ` Elias Oltmanns
     [not found]   ` <1221724782.3261.13.camel@raz>
2008-09-19  9:50     ` [PATCH 4/4 v2] Add documentation for hard disk shockprotection interface Elias Oltmanns
2008-09-19 20:03       ` raz ben yehuda
2008-09-19 22:05         ` Elias Oltmanns
2008-09-20 23:25           ` 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=48D58655.5060300@kernel.org \
    --to=tj@kernel.org \
    --cc=eo@nebensachen.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=razb@bitband.com \
    /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).