From: "Carl A. Cook" <CACook@quantum-equities.com>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: linux disk access when idle
Date: Fri, 21 Aug 2009 16:13:27 -0700 [thread overview]
Message-ID: <200908211613.28075.CACook@quantum-equities.com> (raw)
In-Reply-To: <20090821231039.GB22331@sewage>
I haven't followed this whole thread, but there is some aspect of ext3 journalling which hits that disk with regularity. Obviously not a write flush, but some sort of check out of insecurity or something.
On Friday 21 August 2009 16:10:39 Matt Garman wrote:
> On Fri, Aug 21, 2009 at 06:00:43PM -0400, Bill Davidsen wrote:
> > /proc/sys/vm/dirty_expire_centisecs still set to 30 sec?
>
> $ cat /proc/sys/vm/dirty_expire_centisecs
> 2999
>
> Yup. Maybe I don't understand exactly what this does, but if the
> drives are idle (i.e. no reads or writes) for say an hour or more,
> why would there be any dirty data to flush?
>
> That's why I'm confused---this machine literally goes for hours at a
> time without and read or write attemps on these drives.
>
> -Matt
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-08-21 23:13 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
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 [this message]
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=200908211613.28075.CACook@quantum-equities.com \
--to=cacook@quantum-equities.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).