From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: noatime,nodiratime?
Date: Wed, 26 May 2010 16:53:33 +0200 [thread overview]
Message-ID: <201005261653.33774@zmi.at> (raw)
In-Reply-To: <4BF47859.6020808@hardwarefreak.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 598 bytes --]
On Donnerstag, 20. Mai 2010 Stan Hoeppner wrote:
> Yes. It would be nice to see the settings regardless of default or
> user defined.
I second that. Because you could use barrier in the fstab options, but
it's not supported and so nobarrier is used. It would be good to check
that by simply "cat /proc/mounts".
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-26 14:51 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 ` Michael Monnerie [this message]
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=201005261653.33774@zmi.at \
--to=michael.monnerie@is.it-management.at \
--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.