All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elias Oltmanns <eo@nebensachen.de>
To: raz ben yehuda <razb@bitband.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 4/4 v2] Add documentation for hard disk shockprotection interface
Date: Sat, 20 Sep 2008 00:05:08 +0200	[thread overview]
Message-ID: <87ej3f7pwr.fsf@denkblock.local> (raw)
In-Reply-To: <1221854586.7473.16.camel@raz> (raz ben yehuda's message of "Fri, 19 Sep 2008 22:03:06 +0200")

raz ben yehuda <razb@bitband.com> wrote:
> On Fri, 2008-09-19 at 11:50 +0200, Elias Oltmanns wrote:
>> "Raz Ben-Yehuda" <razb@bitband.com> wrote:
>> > Elias
>> > looks very interesting.
>> > 1. How will it impact VM , swappers , raids ?  
>> 
>> What exactly do you want to know? As long as the disk is parked, you can
>> do no I/O on it, i.e. no swapping is possible. Since I don't know
>> anything about the implementation of raids and don't have a raid setup
>> here, I can't really tell how a raid device will behave exactly when one
>> of its disks has been parked. Generally, all I/O will be delayed until
>> the disk is unparked again.
>> > 2. you said it has no value for servers ? did you try ?
>> 
>> Again, I'm not quite sure what you want to know. Obviously, desktops or
>> servers for that matter can have disks installed that support the unload
>> feature. On these devices you can use the interface as described in my
>> document. All I'm saying is that the interface has been designed with
>> laptops in mind because I don't see in which situation immediate head
>> unloading would be required or even desirable in a classical server
>> environment.
> I will rephrase. does head parking increase reliability ( MTBF ... MTTF ) of a disk ? 
> My servers hardly generate IOs at night times, does head parking at nights extend 
> the life of a disk ? or is it the opposite ? does it matter ?

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.

Hope that helps,

Elias

  reply	other threads:[~2008-09-20  5:54 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 [this message]
2008-09-20 23:25           ` Tejun Heo

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=87ej3f7pwr.fsf@denkblock.local \
    --to=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 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.