From owner-freebsd-questions@FreeBSD.ORG Thu May 13 15:01:19 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1CC516A4CE for ; Thu, 13 May 2004 15:01:19 -0700 (PDT) Received: from pfepc.post.tele.dk (pfepc.post.tele.dk [195.41.46.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3041C43D41 for ; Thu, 13 May 2004 15:01:19 -0700 (PDT) (envelope-from xi@borderworlds.dk) Received: from ferengi.borderworlds.dk (0x50a69807.arcnxx19.adsl-dhcp.tele.dk [80.166.152.7]) by pfepc.post.tele.dk (Postfix) with ESMTP id 098E7262822 for ; Fri, 14 May 2004 00:01:17 +0200 (CEST) Received: from borg.borderworlds.dk (localhost [127.0.0.1]) by ferengi.borderworlds.dk (Postfix) with ESMTP id 3F73FB806 for ; Fri, 14 May 2004 00:01:17 +0200 (CEST) Received: by borg.borderworlds.dk (Postfix, from userid 1001) id 0F3C2B823; Fri, 14 May 2004 00:01:17 +0200 (CEST) Sender: xi@borderworlds.dk To: freebsd-questions@freebsd.org References: <40A32D0F.5050101@yahoo.co.uk> <200405132247.33270.peter.schuller@infidyne.com> From: Christian Laursen Date: 14 May 2004 00:01:16 +0200 In-Reply-To: <200405132247.33270.peter.schuller@infidyne.com> Message-ID: <86isf0dm1f.fsf@borg.borderworlds.dk> Lines: 17 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: The journalling file system saga X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 May 2004 22:01:19 -0000 Peter Schuller writes: [Problems with softupdates] > Yet another problem is that an fsync() no longer guarantees that data is on > disk, even with write caching disabled on the media. This doesn't break > things like PostgreSQL provided that the order of writes is preserved, but it > does break things like MTA:s that want to guarantee that critical data has > been commited to persistent storage before signaling success to an external > entity (SMTP client). fsync(2) works as advertised with softupdates enabled so that shouldn't cause any problems for applications that are written properly. -- Med venlig hilsen Christian Laursen