From owner-freebsd-hackers  Mon Jan 13 13:13:45 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id NAA05634
          for hackers-outgoing; Mon, 13 Jan 1997 13:13:45 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA05600
          for <freebsd-hackers@freebsd.org>; Mon, 13 Jan 1997 13:12:41 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA28218; Mon, 13 Jan 1997 13:59:54 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199701132059.NAA28218@phaeton.artisoft.com>
Subject: Re: mount -o async on a news servre
To: bde@zeta.org.au (Bruce Evans)
Date: Mon, 13 Jan 1997 13:59:54 -0700 (MST)
Cc: dg@root.com, terry@lambert.org, freebsd-hackers@freebsd.org,
        henrich@crh.cl.msu.edu
In-Reply-To: <199701130626.RAA07882@godzilla.zeta.org.au> from "Bruce Evans" at Jan 13, 97 05:26:31 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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.

"Shall be marked for update".

The question for the rest of it is "does 'shall be updated' mean 'shall
be written to disk'"?  ...most FS designers I've talked to say "no".


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.