public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: xfs@oss.sgi.com
Subject: Re: noatime,nodiratime?
Date: Thu, 27 May 2010 09:18:42 +1000	[thread overview]
Message-ID: <20100526231842.GC1395@dastard> (raw)
In-Reply-To: <4BF47859.6020808@hardwarefreak.com>

On Wed, May 19, 2010 at 06:46:33PM -0500, Stan Hoeppner wrote:
> Eric Sandeen put forth on 5/19/2010 2:50 PM:
> 
> > 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*
> 
> IMHO the option values should be listed, whether they are the defaults or
> user defined.  XFS may be breaking convention by doing so, as it appears
> EXT2 (and probably 3/4, and other filesystems) behave the same as XFS
> currently does--no display of default settings, except rw.
> 
> > It's so hard to keep google up to date ;)
> 
> Add the information to the FAQ and it'll show up in Google indexes in short
> order, assuming you allow robots to crawl xfs.org, which IIRC, you do.
> 
> > /proc/mounts shows all mount options which were set differently from
> > defaults.
> 
> Yes.  It would be nice to see the settings regardless of default or user
> defined.  In the absence of, or in addition to this, could we get a
> consistent (default) for each setting in XFS man mount?  For example,
> barrier is listed but we're not told if it's the default.  nobarrier isn't
> even in the man page, but it's on the wiki FAQ.  The wiki FAQ tells us that
> barrier is the default.  I'm referring to the man page that comes with
> Debian 5.0.  The current man page may be updated to reflect some of these
> things, though I've not read it yet.
>
> Sorry if I seem nit-picky.  I've spent many hours trying to hunt down some
> of this information and it's been a frustrating process.  XFS rocks.
> Currently, from here, the docs don't rock yet. :(

Patches to fix up the docs will be gratefully accepted. :)
Patches to change the output of /proc/mounts might take a little
more discussion....

Note that the man pages for mount are in the util-linux package, not
anything XFS...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2010-05-26 23:16 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     ` noatime,nodiratime? Eric Sandeen
2010-05-19 23:46       ` noatime,nodiratime? Stan Hoeppner
2010-05-26 14:53         ` noatime,nodiratime? Michael Monnerie
2010-05-26 23:18         ` Dave Chinner [this message]

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=20100526231842.GC1395@dastard \
    --to=david@fromorbit.com \
    --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