Christoph Hellwig put forth on 5/19/2010 1:23 PM:
> On Wed, May 19, 2010 at 09:13:38AM -0500, Stan Hoeppner wrote:
>> Need a little education here. I have a general understanding of what the
>> inode access timestamps "are" but I have no idea what, if any, applications
>> make use of these access times. I see posts all over Google land saying to
>> use "noatime,nodiratime,logbufs=8" for XFS mount options to increase
> Which doesn't make much sense. First 8 log buffers has been the default
> for XFS for a long time. Second nodiratime has always been useless as
> it is a strict subset of of noatime. Now noatime isn't the default yet,
> but instead relatime is, which still updates the atime in memory, but
> only writes it back when the inode has other changes, or on umount.
> It should give you equivalent performance to noatime, but better
Wow. That'll teach me to trust that man pages are accurate. :) Maybe you
could add this explanation about relatime vs noatime to the man page as well.
Any chance xfs_info could be updated to output the information we're
discussing, including spitting out the XFS specific mount options that are
currently active at the time of running xfs_info? There seems to be much
confusion in the community due to lack of accurate information being
available. Google for "XFS performance" and you'll see
"noatime,nodiratime,logbufs=8" mentioned consistently from early 2000's to
the present as a performance enhancer.
If what you say is true, on my 188.8.131.52 system, I actually decreased logbufs
from 8 to 4 half an hour ago, instead of increasing it from 2 to 4, as man
lead me to believe I was doing. Do any of the xfs tools output the XFS
specific active mount options allowing an op to confirm changes? As someone
else stated it would be nice to be able to see these parameter values. As
is, AFAICT, there's no way to confirm these parameter values.