Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.kei.com!news.mathworks.com!fu-berlin.de!news.dfn.de!RRZ.Uni-Koeln.DE!news.rhrz.uni-bonn.de!comma.rhein.de!not-for-mail
From: mlelstv@comma.rhein.de (Michael van Elst)
Newsgroups: comp.unix.bsd.freebsd.misc,comp.os.linux.development.system
Subject: Re: async or sync metadata [was: FreeBSD v. Linux]
Date: 11 Feb 1996 13:58:49 +0100
Organization: Regionalnetz Bonn eV
Lines: 16
Message-ID: <4fkp69$rpj@comma.rhein.de>
References: <4er9hp$5ng@orb.direct.ca> <4f9skh$2og@dyson.iquest.net> <DMI5Mt.768@pe1chl.ampr.org> <4fi6gq$3tr@dyson.iquest.net> <4fjodc$o8j@venger.snds.com>
NNTP-Posting-Host: comma.rhein.de
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:14057 comp.os.linux.development.system:17656
In <4fjodc$o8j@venger.snds.com> grif@hill.ucr.edu (Michael Griffith) writes:
> sync metadata with async data is not just slower,
> it is LESS SAFE.
I think this discussion is pretty ancient and the result was that
"async data" doesn't mean that the metadata is updated before the
data is committed but _after_.
The result is that the metadata always reflects a consistent state,
wether the data is written async or not. With async data it doesn't
necessarily reflect the last state though.
--
Michael van Elst
Internet: mlelstv@mpifr-bonn.mpg.de mlelstv@serpens.rhein.de
"A potential Snark may lurk in every tree."