From: Goswin von Brederlow <goswin-v-b@web.de>
To: Matt Garman <matthew.garman@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: linux disk access when idle
Date: Sat, 22 Aug 2009 08:33:37 +0200 [thread overview]
Message-ID: <874os0l5mm.fsf@frosties.localdomain> (raw)
In-Reply-To: <20090821165935.GA18915@sewage> (Matt Garman's message of "Fri, 21 Aug 2009 11:59:35 -0500")
Matt Garman <matthew.garman@gmail.com> writes:
> On Fri, Aug 21, 2009 at 06:45:45AM +1200, Richard Scobie wrote:
>> Matt Garman wrote:
>>> So what I'm trying to figure out is, what is causing the disk
>>> access? It could be any one of:
>>>
>>> - Kernel
>>> - RAID subsystem (i.e. md)
>>> - XFS filesystem
>>> - NFS
>>> - Samba
>>> - ???
>>
>> Are you running smartd? It polls the drives every 30minutes.
>
> I was running smartd, until I received your post :)
>
> Unfortunately, this does not help keep the heads parked any longer.
>
> Nonetheless, thank you for the hint.
>
> Matt
Smartd has an option not to wake up disks. If you have smartd scann
less often than the suspend time of the disk then idle disk can spinn
down and stay that way.
MfG
Goswin
next prev parent reply other threads:[~2009-08-22 6:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 16:35 linux disk access when idle Matt Garman
2009-08-20 18:45 ` Richard Scobie
2009-08-21 16:59 ` Matt Garman
2009-08-21 17:01 ` Ric Wheeler
2009-08-22 21:04 ` Matt Garman
2009-08-23 18:23 ` Bill Davidsen
2009-08-26 19:45 ` Matt Garman
2009-08-22 6:33 ` Goswin von Brederlow [this message]
2009-08-21 6:42 ` Henry, Andrew
2009-08-21 8:17 ` Jon Hardcastle
2009-08-21 16:35 ` Foster_Brian
2009-08-21 17:31 ` Matt Garman
2009-08-21 17:22 ` Matt Garman
2009-08-21 22:00 ` Bill Davidsen
2009-08-21 23:10 ` Matt Garman
2009-08-21 23:13 ` Carl A. Cook
2009-08-22 1:41 ` berk walker
2009-08-22 2:07 ` John Robinson
2009-08-22 4:28 ` Richard Scobie
2009-08-22 5:04 ` Tapani Tarvainen
2009-08-22 6:37 ` Goswin von Brederlow
2009-08-24 18:07 ` Billy Crook
2009-08-22 5:02 ` Kyle Liddell
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=874os0l5mm.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=linux-raid@vger.kernel.org \
--cc=matthew.garman@gmail.com \
/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