From: Eric Sandeen <sandeen@sandeen.net>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: xfs@oss.sgi.com
Subject: Re: noatime,nodiratime?
Date: Wed, 19 May 2010 14:50:29 -0500 [thread overview]
Message-ID: <4BF44105.4040902@sandeen.net> (raw)
In-Reply-To: <4BF43B3C.6030403@hardwarefreak.com>
On 05/19/2010 02:25 PM, Stan Hoeppner wrote:
> 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?
xfs_info actually calls xfs_growfs -n, and it's only reporting on-disk
geometry. I kind of doubt that'll change. If you want to see mount
options, /proc/mounts is the place ... but then we don't show the
defaults ;) I wonder if we should change that and be explicit about
every option in /proc/mounts *shrug*
> 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.
It's so hard to keep google up to date ;)
> If what you say is true, on my 2.6.32.9 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.
/proc/mounts shows all mount options which were set differently from
defaults.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-19 19:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 14:13 noatime,nodiratime? Stan Hoeppner
2010-05-19 17:33 ` noatime,nodiratime? Nicolas KOWALSKI
2010-05-19 18:00 ` noatime,nodiratime? Stan Hoeppner
2010-05-19 18:24 ` noatime,nodiratime? Christoph Hellwig
2010-05-19 19:10 ` noatime,nodiratime? Nicolas KOWALSKI
2010-05-19 18:23 ` noatime,nodiratime? Christoph Hellwig
2010-05-19 19:25 ` noatime,nodiratime? Stan Hoeppner
2010-05-19 19:50 ` Eric Sandeen [this message]
2010-05-19 23:46 ` noatime,nodiratime? Stan Hoeppner
2010-05-26 14:53 ` noatime,nodiratime? Michael Monnerie
2010-05-26 23:18 ` noatime,nodiratime? Dave Chinner
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=4BF44105.4040902@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.