On Thu, 2008-01-31 at 12:12 +0100, Bent Terp wrote:
> On Jan 30, 2008 5:39 PM, William L. Maltby <CentOS4Bill@xxxxxxxxxxxx> wrote:
> > According to man pages for mount and nfs, *atime is not a supported
> > mount option for NFS. *If* I read correctly.
AAAAAAAAAAAAAAAAAAAAAA
TG I said this. ||||||||||||||||||||||
>
> I don't agree. noatime is listed in the general section of man mount,
> and those options should then exist (but may be ignored) by nfs. man
> nfs explains the differences between v3 and v4. In
> Documentation/filesystems there aren't any caveats either.
Well, although it's been a millennium, I seem to recall using that
option for NFS mounts in the past. "His curiosity piqued, the sleuth is
irresistibly drawn into a brief diversion from his pastime to see what
can be discovered!".
Hmmm... from man mount
---------------- Edited for readability --------------------------------
-o Options are specified with a -o flag followed by a comma
separated string of options. Some of these options are only
useful when they appear in the /etc/fstab file. The following
options apply to any file system that is being mounted
--->>> (but not every file system actually honors them - e.g., the sync
option today has effect only for ext2, ext3, fat, vfat and ufs):
------------------------------------------------------------------------
>From man nfs, following "Options for the nfs file system type" and for
the NFS4 section as well, there is no mention of (no)atime.
Johnny's attempted tests, IIRC, erred when attempting to use it, but
there were other options so it is not conclusive.
Logical, but possibly erroneous conclusion: unsupported. However, I know
that man pages can be incomplete, inaccurate and ambiguous. So what does
one do?
$ grep -irl atime /usr/share/system-config-nfs
And as a check I didn't goofus the previous command:
$ grep -irl sync /usr/share/system-config-nfs
/usr/share/system-config-nfs/propertiesWindow.py
/usr/share/system-config-nfs/nfsBackend.pyc
/usr/share/system-config-nfs/nfsBackend.py
/usr/share/system-config-nfs/nfs-export.pyc
/usr/share/system-config-nfs/propertiesWindow.pyc
/usr/share/system-config-nfs/nfsData.py
/usr/share/system-config-nfs/nfsData.pyc
/usr/share/system-config-nfs/nfs-export.py
$
Ahhh... but still, maybe it's just not included in the default setup
scripts.
$ (cd /usr/share/doc/; grep -irl atime system-config-nfs* libnfsidmap*)
$ (cd /usr/share/doc/; grep -irl sync system-config-nfs* libnfsidmap*)
system-config-nfs-1.2.8/config.html
$
>
> Anyways, we didn't change mount options when upping the kernel.
Still, we can't believe that an option you've never changed, and
apparently worked before, and is not specifically (in)excluded as
(un)supported is unsupported now. :-(
I'm *not* being wise-ass, just acknowledging that sometimes all locally
available (excluding "read the SOURCE Luke!") references does not tell
us all that we may need to know. So I go googling... and see refs all
over the place that indicate noatime is being used.
There are admonishments, such as "no -o", "separate options with commas
and no spaces", etc.
Maybe there is an answer in the Googlevers? Maybe support for it has
been dropped (I hope not).
Last,
$ rpm -q --changelog nfs-utils|grep -i atime
"No joy in Mudville".
Anyway, my curiosity has *not* been satisfied, but I've got other
interests pulling at me now.
BTW: man mount points out that some of the commands are only effective
when invoked within the /etc/fstab. JIC.
>
> regards,
> Bent
<snip sig stuff>
Good luck with it.
--
Bill
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
