From: Eric Sandeen <sandeen@sandeen.net>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfssyncd and disk spin down
Date: Fri, 24 Dec 2010 21:36:49 -0600 [thread overview]
Message-ID: <4D1566D1.6090506@sandeen.net> (raw)
In-Reply-To: <4D1525FB.1010605@hardwarefreak.com>
On 12/24/10 5:00 PM, Stan Hoeppner wrote:
> Petre Rodan put forth on 12/24/2010 12:02 AM:
>
>>> fs.xfs.xfssyncd_centisecs (Min: 100 Default: 3000 Max: 720000)
>>> fs.xfs.age_buffer_centisecs (Min: 100 Default: 1500 Max: 720000)
>>
>> just increasing the delay until an inevitable and seemingly redundant disk write is not what I want.
>> I was searching for an option to make internal xfs processes not touch the drive after the buffers/log/dirty metadata have been flushed (once).
>
> I'm not a dev Petre but just another XFS user. This is the best
> "solution" I could come up with for your issue. I assumed this
> "unnecessary" regularly scheduled activity was a house cleaning measure
> and done intentionally; didn't dawn on me that it may be a bug.
>
> Sorry I wasn't able to fully address your issue. If/until there is a
> permanent fix for this you may want to bump this to 720000 anyway as an
> interim measure, if you haven't already, as it should yield a
> significantly better situation than what you have now. You'll at least
> get something like ~1400 minutes of sleep per day instead of none,
> decreasing your load/unload cycles from ~2880/day to ~120/day, if my
> math is correct.
Of course, then xfssyncd will not be doing its proper duty regularly ;)
We just need to see why it's always finding work to do when idle.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-12-25 3:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 16:55 xfssyncd and disk spin down Petre Rodan
2010-12-23 19:29 ` Stan Hoeppner
2010-12-23 21:16 ` Petre Rodan
2010-12-24 0:54 ` Stan Hoeppner
2010-12-24 5:15 ` Stan Hoeppner
2010-12-24 6:02 ` Petre Rodan
2010-12-24 23:00 ` Stan Hoeppner
2010-12-25 3:36 ` Eric Sandeen [this message]
2010-12-25 4:32 ` Stan Hoeppner
2010-12-24 18:17 ` Eric Sandeen
2010-12-25 12:09 ` Petre Rodan
2010-12-27 2:19 ` Dave Chinner
2010-12-27 6:16 ` Petre Rodan
2010-12-27 14:07 ` Dave Chinner
2010-12-27 17:19 ` Petre Rodan
2010-12-31 0:13 ` Dave Chinner
2011-01-20 10:01 ` Petre Rodan
2011-01-20 11:06 ` Dave Chinner
2011-01-20 12:07 ` Petre Rodan
2011-01-20 13:24 ` Christoph Hellwig
2011-01-20 23:43 ` Dave Chinner
2011-02-10 20:42 ` Petre Rodan
2011-02-10 22:18 ` Dave Chinner
2011-02-14 18:04 ` Brian Duncan
2011-05-31 14:40 ` Brian Duncan
2011-05-31 15:16 ` Michael Weissenbacher
2011-06-01 23:37 ` Dave Chinner
2011-07-11 4:02 ` Brian Duncan
2011-07-11 14:34 ` Michael Weissenbacher
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=4D1566D1.6090506@sandeen.net \
--to=sandeen@sandeen.net \
--cc=stan@hardwarefreak.com \
--cc=xfs@oss.sgi.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