Benches Deployment and MDM

7

noatime / nodiratime on Xserve

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

We've inherited a large installation with Xserve and Xserve RAID, as well as storage from a couple of other vendors. I have a general question, and at the moment do not have access to the unit to gather detailed information.

Are the noatime / nodiratime mount options supported on the Xserve? If so, what OS level would be required, and how would I go about using them? Can it be changed while the filesystems are online? I know the units do not have Intel CPUs, I believe they are G5. I'm not in a position to do very much to them without a maintenance window planned with considerable lead time.

The nature of the system is such that there are tens of millions of small files, so we could benefit greatly from not having the atime field updated on files and directories whenever they are read. I've done a lot of Internet searching and can't find anything definitive. Almost everything I've found has to do with Linux, and I've already taken care of this on all our Linux systems.

If there's any information anyone might need to research this, let me know, and include instructions on how to get it. I have very little experience with OS X, but I'm familiar with Linux.

7 replies

Sign in or join Beachball Help to reply.

  1. 0

    Tod Kuykendall

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hello elyograg, and welcome to the Apple boards,

    If the Xserves are running OS X on HFS+ disks then I
    think that setting noatime (at least on System disks) may result in unpredictable behavior. I'm no Linux guru but keeping track of last access and modified times are pretty deeply attached to the OS functions in OS X and with HFS+. If the OS X boxen are sharing foreign disks with a Linux box that is also running noatime then maybe you'll be okay.

    I think the closest kind of win you can achieve on the OS X/HFS+ side to turn off journalling at the disk level if you have it on. Journalling is optional with HFS+ and does add security and integrity but at the cost of time.

    From the practical side OS X observes fstab on mount and the usual options ( *mount -o noatime* )apply but unless the Xserve is mounting a foreign disk system I would hesitate to mess with the default mount options too much. Also keep in mind that OS X apps like Disk Utility will probably ignore fstab settings so don't depend on users never being able to override a particular setting (like read-only).

    Hope that helps,

    =Tod

    PS More tech details on Mount are here:
    http://www.osxfaq.com/man/8/mount.ws

  2. 0

    elyograg

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    The filesystems that I want to mount with noatime are several fibre channel attached devices including Xserve RAID units, mounted from the controlling Xserve via NFS on a collection of Solaris machines. The Xserve's built in disks are not exported and I did not plan on messing with those.

    As far as I have been told by the developers, the Solaris software that uses the storage doesn't care about the atime field, only the mtime field. Before taking this beyond the drawing board, I will have that verified explicity.

    Am I right in thinking that from what you've said and the information on the mount command, I should be OK with using noatime? There are no OS X files on the attached storage.

  3. 0

    elyograg

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    That was potentially confusing, so I'll restate it.

    There are several fibre channel devices plugged into a switch along with the Xserve pair. The Xserve exports the filesystems via NFS to the production Sun servers.

    We have a database with about 20 million objects, mostly JPEG photos. Each object has at least five files in the filesystem associated with it. There are files for up to 1000 objects in each subdirectory. This means that walking the file tree for backup or statistical purposes results in millions of atime updates. The resulting combination of read and write I/O causes occasional performance issues for the production system.

  4. 0

    Tod Kuykendall

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    This way too specific a situation for me to say "Sure it'll work!" but given the way you've laid it out it does seem like it would be okay. I also can't testify to what kind of performance gain you will or won't receive from making the change.

    Basically OS X is BSD at the file system level which should feel pretty familiar to you coming from Linux. Apple then layers a bunch of convenience class stuff on top of the lower layers to make it "just work" at the consumer system level. As long as you're not looking for that shiny stuff to work then you can muck at the file system level without losing anything. Where *nix admins get bit is that often Apple rewrites those preferences from one of those convenience classes so the classic *nix conf file changes don't stick - especially after reboot. (But fstab changes will.)

    My $.02,

    =Tod

    PS If you try it report back on the results when you get a chance.

  5. 0

    elyograg

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I've finally gotten access to the CLI, and checked the man page for mount. There's no mention of atime or noatime in the man page. The following command returns nothing:

    strings /sbin/mount* | grep -i atime

    This suggests that, as of 10.4.7, the option doesn't exist on my hardware. Can you confirm that it's available in a newer release of 10.4?

  6. 0

    elyograg

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Assuming I can get this supported, can the change be made while the system is online? Such a remount can be done in Linux, but OS X may be different.

  7. 0

    Tod Kuykendall

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Yeah, some references list noatime under -o options but others don't. It looks to me like the OS X shell command line
    mount doesn't support it but the
    bash version of
    mount does.

    http://www.ss64.com/osx/mount.html


    http://www.ss64.com/bash/mount.html

    I can find concrete references to Darwin using
    noatime but only in reference to UFS volumes. I thought it was more straightforward than this but I'm not currently sure if the docs are lifted from BSD and are wrong or if OS X has discarded/ignored the
    noatime command since it uses nonstandard disk systems or some more complex combination of these.

    I'll look into it further and let you know if I get a definitive answer.

    =Tod