From owner-freebsd-hackers Thu Jun 19 10:10:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06318 for hackers-outgoing; Thu, 19 Jun 1997 10:10:26 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA06311 for ; Thu, 19 Jun 1997 10:10:23 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA22674; Thu, 19 Jun 1997 10:00:38 -0700 From: Terry Lambert Message-Id: <199706191700.KAA22674@phaeton.artisoft.com> Subject: Re: update question. To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Thu, 19 Jun 1997 10:00:38 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Jaye Mathisen" at Jun 18, 97 11:18:30 am 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 > Does update only affect UFS operations? If I have nfs set to async, will > update sync it up? Update syncs dirty buffers for all mounted FS's. Unless NFS is mounted async (a violation of the RFC's defining the NFS protocol, for the most part), all ops will be synchronous anyway so that network outages do not leave implied state indeterminate. For example, a data file and a seperate index file which indexes records in the first file must be guaranteed colinear updating so that the database can be deterministically recovered following a client or server crash with a trasaction pending. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.