All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Campbell <lists2009@fnarfbargle.com>
To: Patrick Gautschi <patrick@gautschi.net>,
	Peter Grandi <pg@lxra2.for.sabi.co.UK>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Disks never stop spinning
Date: Fri, 14 Nov 2014 12:11:36 +0800	[thread overview]
Message-ID: <546580F8.2040607@fnarfbargle.com> (raw)
In-Reply-To: <54657187.6020306@gautschi.net>

On 14/11/14 11:05, Patrick Gautschi wrote:
>>    #  hddtemp /dev/sd[bcdef]
>>    /dev/sdb: SAMSUNG HD103UJ: drive is sleeping
>>    /dev/sdc: WDC WD10EZEX-22RKKA0: drive is sleeping
>>    /dev/sdd: ST1000DM003-9YN162: drive is sleeping
>>    /dev/sde: SAMSUNG HD103SJ: drive is sleeping
>>    /dev/sdf: WDC WD10EZEX-22RKKA0: drive is sleeping
>
> Different disks; looks like desktop types.
>
>> That means something else is waking up those disks. To verify
>> this use something like:
>
> FS are not mounted and arrays stopped. There is nothing that wakes them up.
> If a switch them off manually with hdparm -Y they stay off.
>

Are you polling them with smartmontools? I have a unit here where I had 
to add the "standby" :

DEVICESCAN -s (L/../../7/07|S/../../[1-6]/00) -n standby,q -m root -M 
exec /usr/share/smartmontools/smartd-runner

.. clause in smartd.conf. This ensures smartd does not wake the disk 
every 15 minutes for it's poll, and only polls if the drive is already 
spinning.

Failing that, I'd put it to sleep and it'd wake up on the next 15 
minutes smart poll.

Regards,
Brad

  reply	other threads:[~2014-11-14  4:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 18:44 Disks never stop spinning P. Gautschi
2014-11-13 14:05 ` Peter Grandi
2014-11-14  3:05   ` Patrick Gautschi
2014-11-14  4:11     ` Brad Campbell [this message]
2014-12-04 19:33     ` Phillip Susi
2014-12-06 15:16       ` P. Gautschi
2014-12-08 20:38         ` Phillip Susi

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=546580F8.2040607@fnarfbargle.com \
    --to=lists2009@fnarfbargle.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=patrick@gautschi.net \
    --cc=pg@lxra2.for.sabi.co.UK \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.