From: Matthias Schniedermeyer <ms@citd.de>
To: Felix Blyakher <felixb@sgi.com>
Cc: Michael Weissenbacher <mw@dermichi.com>, xfs@oss.sgi.com
Subject: Re: XFS and atime update strangeness
Date: Tue, 23 Jun 2009 18:35:35 +0200 [thread overview]
Message-ID: <20090623163535.GA12551@citd.de> (raw)
In-Reply-To: <AE31FB8A-6C11-4177-85AB-794839A88080@sgi.com>
On 23.06.2009 10:01, Felix Blyakher wrote:
> On Jun 19, 2009, at 4:36 AM, Michael Weissenbacher wrote:
>
>> Is there any way to enable permanent atime updates in case someone
>> wants them?
>
> That's another good request I'd like to address as well. The
> above mentioned patch just makes it behave as relatime.
Just to have it explictly mentioned a.k.a. just for the record.
strictatime is AWOL.
With current 2.6.30 you just can't have 'atime' because default was
changed to 'relatime' and the former default got the new option
'strictatime'(*). But if i want to mount a XFS-filesystem strictatime:
XFS: unknown mount option [strictatime]
*:
According to fs/namespace.c, line 795 and following these 4
atime-related options appear to be allowed:
{ MNT_NOATIME, ",noatime" },
{ MNT_NODIRATIME, ",nodiratime" },
{ MNT_RELATIME, ",relatime" },
{ MNT_STRICTATIME, ",strictatime" },
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-06-23 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 9:36 XFS and atime update strangeness Michael Weissenbacher
2009-06-23 15:01 ` Felix Blyakher
2009-06-23 16:35 ` Matthias Schniedermeyer [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=20090623163535.GA12551@citd.de \
--to=ms@citd.de \
--cc=felixb@sgi.com \
--cc=mw@dermichi.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