From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Marc L. de Bruin" Subject: Re: Can't get drives containing spare devices to spindown Date: Thu, 22 Jun 2006 07:22:07 +0200 Message-ID: <449A28FF.20504@debruin.org> References: <446395C0.5060502@debruin.org> <449A2152.2040906@debruin.org> <17562.9479.533427.960138@cse.unsw.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <17562.9479.533427.960138@cse.unsw.edu.au> Sender: linux-raid-owner@vger.kernel.org To: Neil Brown Cc: linux-raid@vger.kernel.org List-Id: linux-raid.ids 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 >>>' 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.