Messages in this thread | | | Date | Sun, 14 Oct 2007 17:05:12 -0500 | From | "Mark Weber" <> | Subject | Re: hdparm standby timeout not working for WD raptors? |
| |
On 10/14/07, Bart Samwel <bart@samwel.tk> wrote: > > Just to be sure: you did use -S 60 to get 5 minutes, right?
Yes. And hdparm is kind enough to print:
/dev/sda: setting standby to 60 (5 minutes)
Here's a bizarre sequence which I just noticed: [extraneous blank lines removed for clarity]
>> hdparm -C /dev/sd[abcde] /dev/sda: drive state is: standby /dev/sdb: drive state is: standby /dev/sdc: drive state is: standby /dev/sdd: drive state is: standby /dev/sde: drive state is: standby
>> hdparm -S 60 /dev/sda /dev/sda: setting standby to 60 (5 minutes)
>> hdparm -C /dev/sd[abcde] /dev/sda: drive state is: active/idle /dev/sdb: drive state is: active/idle /dev/sdc: drive state is: standby /dev/sdd: drive state is: standby /dev/sde: drive state is: standby
Note that the -S 60 on /dev/sda affected /dev/sdb too! This is repeatable.
I have these drives as RAID5 (software RAID). I don't know if that has anything to do with the failure of -S or not. Don't know if hdparm bypasses the RAID or not. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |