| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <71b295590710141505x54ca0a8fwebfd75ab4fdf2e71@mail.gmail.com> Date: Sun, 14 Oct 2007 17:05:12 -0500 From: "Mark Weber" <crash@...ysoft.com> To: "Bart Samwel" <bart@...wel.tk> Cc: "Mark Lord" <lkml@....ca>, linux-kernel@...r.kernel.org Subject: Re: hdparm standby timeout not working for WD raptors? On 10/14/07, Bart Samwel <bart@...wel.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@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists