Date: Fri, 15 Mar 2002 19:38:44 +0100 From: Christoph Hellwig <hch@caldera.de> To: Terry Lambert <tlambert2@mindspring.com> Cc: Josh MacDonald <jmacd@CS.Berkeley.EDU>, Parity Error <bootup@mail.ru>, freebsd-fs@FreeBSD.ORG, reiserfs-dev@namesys.com Subject: Re: metadata update durability ordering/soft updates Message-ID: <20020315193844.A26441@caldera.de> In-Reply-To: <3C923C91.454D7710@mindspring.com>; from tlambert2@mindspring.com on Fri, Mar 15, 2002 at 10:25:21AM -0800 References: <E16lReK-000C3T-00@f10.mail.ru> <3C910C57.71C2D823@mindspring.com> <20020315065651.02637@helen.CS.Berkeley.EDU> <3C923C91.454D7710@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 15, 2002 at 10:25:21AM -0800, Terry Lambert wrote: > > - The file system has never made any guarantees. > > Yes it has. If you look at the atime/mtime/ctime update > requirements for the OS, they are pretty blatant. THey > just aren't enough to be able to blindly use them. These requirements are only there for O_SYNC. > > - You can use fsync() to stabilize a single file and its metadata > > dependencies. > > Metadata stabilization should be automatic. What an fsync > there does is really enforce ordering on metadata writes, > by acting as a barrier. Why do you think there is fdatasync() (and O_DSYNC)? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020315193844.A26441>