All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Greg Cormier <gcormier@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Sleeping hard drives in an array?
Date: Thu, 01 May 2008 10:55:04 +0100	[thread overview]
Message-ID: <48199378.5020903@dgreaves.com> (raw)
In-Reply-To: <29a863790804300802i358ab6d9t2be907b47176bd5b@mail.gmail.com>

Greg Cormier wrote:
> Is it possible to sleep hard drives in an array?
yes - to be clear you sleep the drives though, not the array.

> Can I sleep the drives in my RAID5 array while it's not being used?
> It's an XFS partition.
XFS is bad at this IIRC.
Certainly noatime is important to prevent cache accesses from updating the fs.

> 
> But I'm fairly sure they are not spinning down :( Is there some
> activity mdadm is doing in the background?

from Documentation/laptops/laptop-mode.txt:

If you want to find out which process caused the disk to spin up, you can
gather information by setting the flag /proc/sys/vm/block_dump. When this flag
is set, Linux reports all disk read and write operations that take place, and
all block dirtyings done to files. This makes it possible to debug why a disk
needs to spin up, and to increase battery life even more. The output of
block_dump is written to the kernel output, and it can be retrieved using
"dmesg". When you use block_dump and your kernel logging level also includes
kernel debugging messages, you probably want to turn off klogd, otherwise
the output of block_dump will be logged, causing disk activity that is not
normally there.

also google found
http://www.nslu2-linux.org/wiki/FAQ/HowtoIdentifyWhichProcessesAccessDisk

Before going too far, make sure the array is up but not mounted and ensure that
the drives will actually spin down.

David

  parent reply	other threads:[~2008-05-01  9:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 15:02 Sleeping hard drives in an array? Greg Cormier
2008-05-01  8:52 ` Mario 'BitKoenig' Holbe
2008-05-01  9:55 ` David Greaves [this message]
2008-05-02 21:11 ` Bill Davidsen
2008-05-02 22:11   ` berk walker
2008-05-02 22:44     ` David Lethe
2008-05-03  8:19       ` Michael Tokarev
2008-05-03 15:29         ` David Lethe
2008-05-03 15:48           ` Brad Campbell
2008-05-05  0:04     ` Bill Davidsen
2008-05-05  0:12       ` Greg Cormier
2008-05-09 13:20         ` Bill Davidsen

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=48199378.5020903@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=gcormier@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    /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.