| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: xfssyncd and disk spin down |
| From: | Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx> |
| Date: | Thu, 23 Dec 2010 23:15:10 -0600 |
| In-reply-to: | <4D13EF3B.2050401@xxxxxxxxxxxxxxxxx> |
| References: | <20101223165532.GA23813@xxxxxxxxxxxxxxxx> <4D13A30A.3090600@xxxxxxxxxxxxxxxxx> <20101223211650.GA19694@xxxxxxxxxxxxxxxx> <4D13EF3B.2050401@xxxxxxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 |
Stan Hoeppner put forth on 12/23/2010 6:54 PM: > http://www.mjmwired.net/kernel/Documentation/filesystems/xfs.txt > > fs.xfs.xfssyncd_centisecs (Min: 100 Default: 3000 Max: 720000) > The interval at which the xfssyncd thread flushes metadata > out to disk. This thread will flush log activity out, and > do some processing on unlinked inodes. > > Maybe related or also worth mentioning: > > fs.xfs.age_buffer_centisecs (Min: 100 Default: 1500 Max: 720000) > The age at which xfsbufd flushes dirty metadata buffers to disk. These can be found in /proc/sys/fs/xfs and you'd simply ~$ echo 720000 > /proc/sys/fs/xfs/xfssyncd_centisecs to get the maximum 12 minute interval. -- Stan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Anyone using XFS in production on > 20TiB volumes?, Stan Hoeppner |
|---|---|
| Next by Date: | Re: xfssyncd and disk spin down, Petre Rodan |
| Previous by Thread: | Re: xfssyncd and disk spin down, Stan Hoeppner |
| Next by Thread: | Re: xfssyncd and disk spin down, Petre Rodan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |