From: Roland Eggner <edvx1@systemanalysen.net>
To: SGI Project XFS mailing list <xfs@oss.sgi.com>
Subject: XFS ignores all atime related mount options, noatime is always in effect, documentation misses this information
Date: Thu, 18 Dec 2008 19:15:13 +0100 [thread overview]
Message-ID: <200812181915.13962.edvx1@systemanalysen.net> (raw)
On my linux box I tried to achieve regular atime behaviour, tried mount with
no atime related option at all, tried mount options atime, sync,
osyncisosync, .. XFS on plain partitions, on loop devices .. I tried another
kernel (sidux image with kernel 2.6.25-9) ..
My result:
It seems impossible to switch off "noatime" mount option.
atime updates happen only in core, never on disk unless coinciding with other
inode modifications, regardless of specified mount options.
$ uname -a
Linux roland 2.6.23.12roland2 #2 Tue Apr 15 17:10:52 CEST 2008 i686 GNU/Linux
$ zgrep XFS /proc/config.gz
CONFIG_XFS_FS=m
# CONFIG_XFS_QUOTA is not set
CONFIG_XFS_SECURITY=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
# CONFIG_VXFS_FS is not set
In mailing list archive I found
http://oss.sgi.com/archives/xfs/2007-10/msg00168.html
It seems, that 3 years ago an unconditional noatime enforcement has been
introduced.
(1) If this is true, please update documentation accordingly.
Users, who need a filesystem with regular atime behaviour, will no more waste
their time to try XFS, when in fact it is unusable for their particular
requirements.
(2) If I missed a possibility to achieve regular atime behaviour, please
document it in Documentation/filesystems/xfs.txt and in man 8 mount.
Thanks!
--
Roland Eggner
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2008-12-18 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 18:15 Roland Eggner [this message]
2008-12-19 13:01 ` XFS ignores all atime related mount options, noatime is always in effect, documentation misses this information Martin Steigerwald
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=200812181915.13962.edvx1@systemanalysen.net \
--to=edvx1@systemanalysen.net \
--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