From: "Marc L. de Bruin" <marc@debruin.org>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Can't get drives containing spare devices to spindown
Date: Thu, 22 Jun 2006 07:22:07 +0200 [thread overview]
Message-ID: <449A28FF.20504@debruin.org> (raw)
In-Reply-To: <17562.9479.533427.960138@cse.unsw.edu.au>
Neil Brown wrote:
>On Thursday June 22, marc@debruin.org wrote:
>
>
>>Marc L. de Bruin wrote:
>>
>>
>>
>>>Situation: /dev/md0, type raid1, containing 2 active devices
>>>(/dev/hda1 and /dev/hdc1) and 2 spare devices (/dev/hde1 and /dev/hdg1).
>>>
>>>Those two spare 'partitions' are the only partitions on those disks
>>>and therefore I'd like to spin down those disks using hdparm for
>>>obvious reasons (noise, heat). Specifically, 'hdparm -S <value>
>>><device>' sets the standby (spindown) timeout for a drive; the value
>>>is used by the drive to determine how long to wait (with no disk
>>>activity) before turning off the spindle motor to save power.
>>>
>>>However, it turns out that md actually sort-of prevents those spare
>>>disks to spindown. I can get them off for about 3 to 4 seconds, after
>>>which they immediately spin up again. Removing the spare devices from
>>>/dev/md0 (mdadm /dev/md0 --remove /dev/hd[eg]1) actually solves this,
>>>but I have no intention actually removing those devices.
>>>
>>>How can I make sure that I'm actually able to spin down those two
>>>spare drives?
>>>
>>>
>
>This is fixed in current -mm kernels and the fix should be in 2.6.18.
>
>NeilBrown
>
>
Thanks Neil for your quick reply. Would it be possible to elaborate a
bit on the problem and the solution? I guess I won't be on 2.6.18 for
some time...
Marc.
next prev parent reply other threads:[~2006-06-22 5:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 19:51 Can't get drives containing spare devices to spindown Marc L. de Bruin
2006-05-30 16:39 ` Bill Davidsen
2006-06-22 4:49 ` Marc L. de Bruin
2006-06-22 5:05 ` Neil Brown
2006-06-22 5:22 ` Marc L. de Bruin [this message]
2006-06-22 5:32 ` Neil Brown
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=449A28FF.20504@debruin.org \
--to=marc@debruin.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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.