Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!mit-eddie!genrad!decvax!decwrl!sun!gorodish!guy
From: guy@gorodish.UUCP
Newsgroups: comp.unix.wizards,comp.unix.questions,comp.sys.att
Subject: Re: O_SYNC and filesystem updating
Message-ID: <12946@sun.uucp>
Date: Mon, 9-Feb-87 14:53:48 EST
Article-I.D.: sun.12946
Posted: Mon Feb  9 14:53:48 1987
Date-Received: Tue, 10-Feb-87 07:10:24 EST
References: <11470@gatech.EDU>
Sender: news@sun.uucp
Reply-To: guy@sun.UUCP (Guy Harris)
Organization: Sun Microsystems, Mountain View
Lines: 16
Keywords: O_SYNC, System V, reliability? What reliability?
Xref: watmath comp.unix.wizards:895 comp.unix.questions:986 comp.sys.att:168

>By "file status" are we to assume that the write syscall also waits for
>the superblock to be updated due to inode information changing?

No, why?  The only thing in the superblock that would change would be
the free lists of various flavors, and whenever you do an "fsck" they
get rebuilt, so there's no point in guaranteeing their correctness
(they're not state information, they're just hints to the file system
code).

>Also, does it wait for the update of the directory where the file resides
>(e.g. in the event of file creation)?

No.  The only thing it does is guarantee 1) that all writes to the
data blocks of the file are done synchronously, 2) all writes of
indirect blocks of the file are done synchronously, and 3) the inode
is updated synchronously after every write.