mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mark Weber" <crash@treysoft.com>
To: "Bart Samwel" <bart@samwel.tk>
Cc: "Mark Lord" <lkml@rtr.ca>, linux-kernel@vger.kernel.org
Subject: Re: hdparm standby timeout not working for WD raptors?
Date: Sun, 14 Oct 2007 17:05:12 -0500	[thread overview]
Message-ID: <71b295590710141505x54ca0a8fwebfd75ab4fdf2e71@mail.gmail.com> (raw)
In-Reply-To: <471284A7.1060800@samwel.tk>

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.

  reply	other threads:[~2007-10-14 22:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-06 17:11 Mark Weber
2007-10-11 19:37 ` Mark Lord
2007-10-12  5:07   ` Mark Weber
2007-10-12 13:30     ` Mark Lord
2007-10-12 22:19       ` Mark Weber
2007-10-13 12:46         ` Mark Lord
2007-10-14 12:36         ` Bart Samwel
2007-10-14 20:30           ` Mark Weber
2007-10-14 21:05             ` Bart Samwel
2007-10-14 22:05               ` Mark Weber [this message]
2007-10-14 23:40                 ` Mark Lord
2007-10-15  0:02                   ` Mark Weber

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=71b295590710141505x54ca0a8fwebfd75ab4fdf2e71@mail.gmail.com \
    --to=crash@treysoft.com \
    --cc=bart@samwel.tk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome