From owner-freebsd-hackers  Sun Jan 12 22:32:12 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id WAA22281
          for hackers-outgoing; Sun, 12 Jan 1997 22:32:12 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA22270
          for <freebsd-hackers@freebsd.org>; Sun, 12 Jan 1997 22:32:08 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id RAA07882; Mon, 13 Jan 1997 17:26:31 +1100
Date: Mon, 13 Jan 1997 17:26:31 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199701130626.RAA07882@godzilla.zeta.org.au>
To: dg@root.com, terry@lambert.org
Subject: Re: mount -o async on a news servre
Cc: freebsd-hackers@freebsd.org, henrich@crh.cl.msu.edu
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>   The two options are complimentary. i.e., "async" will get you fast file
>creates/deletes, but it doesn't stop the access time from being updated - it
>just delays it until the inode buffer needs to be reclaimed. "noatime" doesn't

Access times are never written to disk immediately when nothing else changes,
except for utimes() on some file systems including ufs.

Bruce