[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47120D65.3080008@samwel.tk>
Date: Sun, 14 Oct 2007 14:36:53 +0200
From: Bart Samwel <bart@...wel.tk>
To: crash@...ysoft.com
CC: Mark Lord <lkml@....ca>, linux-kernel@...r.kernel.org
Subject: Re: hdparm standby timeout not working for WD raptors?
Mark Weber wrote:
> On 10/12/07, Mark Lord <lkml@....ca> wrote:
>> That's interesting.
>>
>> So, either something is regularly accessing/polling the drive,
>> or it just doesn't work with the standby timer.
>>
>> Are there any interesting kernel messages being generated
>> during execution of those commands?
>
> No messages to /var/log/messages as a result of those
> commands; I ran several times and did a sync too, just
> in case.
>
> I very much doubt that something is regularly accessing
> the drives because I have a script that runs every 1/2 hour
> to check and log status. The drives stay "standby" for
> hours (even days) at a time unless I specifically access
> something on the RAID array. Then, they stay "active/idle"
> until I manually set them to "standby".
>
> Anything else you'd like me to try?
Some things to check:
* Run "hdparm -I" on your drive. In the "Capabilities" section there is
a line "Standby timer values", for some drives this mentions a device
specific minimum. I know some drives that ignore any setting below 60
seconds.
* I also know of quite a number of drives where hdparm -B settings
override the -S settings, even if you set the -S settings after the
hdparm -B settings. You could try combinations with various values of
hdparm -B, especially 1 and 255.
Cheers,
Bart
-
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