[Top] [All Lists]

Re: xfssyncd and disk spin down

To: xfs@xxxxxxxxxxx
Subject: Re: xfssyncd and disk spin down
From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Date: Fri, 24 Dec 2010 17:00:11 -0600
In-reply-to: <20101224060246.GA2308@xxxxxxxxxxxxxxxx>
References: <20101223165532.GA23813@xxxxxxxxxxxxxxxx> <4D13A30A.3090600@xxxxxxxxxxxxxxxxx> <20101223211650.GA19694@xxxxxxxxxxxxxxxx> <4D13EF3B.2050401@xxxxxxxxxxxxxxxxx> <20101224060246.GA2308@xxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv: Gecko/20101207 Thunderbird/3.1.7
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.


<Prev in Thread] Current Thread [Next in Thread>