From owner-freebsd-fs Fri Mar 15 10:39:45 2002 Delivered-To: freebsd-fs@freebsd.org Received: from ns.caldera.de (ns.caldera.de [212.34.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 71B0337B404 for ; Fri, 15 Mar 2002 10:39:38 -0800 (PST) Received: (from hch@localhost) by ns.caldera.de (8.11.6/8.11.6) id g2FIciS26567; Fri, 15 Mar 2002 19:38:44 +0100 Date: Fri, 15 Mar 2002 19:38:44 +0100 From: Christoph Hellwig To: Terry Lambert Cc: Josh MacDonald , Parity Error , freebsd-fs@FreeBSD.ORG, reiserfs-dev@namesys.com Subject: Re: metadata update durability ordering/soft updates Message-ID: <20020315193844.A26441@caldera.de> References: <3C910C57.71C2D823@mindspring.com> <20020315065651.02637@helen.CS.Berkeley.EDU> <3C923C91.454D7710@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C923C91.454D7710@mindspring.com>; from tlambert2@mindspring.com on Fri, Mar 15, 2002 at 10:25:21AM -0800 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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