From owner-freebsd-fs@FreeBSD.ORG Tue May 18 03:13:40 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8572A16A4CE; Tue, 18 May 2004 03:13:40 -0700 (PDT) Received: from VARK.homeunix.com (adsl-68-122-7-9.dsl.pltn13.pacbell.net [68.122.7.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C41943D99; Tue, 18 May 2004 03:13:23 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: from VARK.homeunix.com (localhost [127.0.0.1]) by VARK.homeunix.com (8.12.10/8.12.10) with ESMTP id i4IACaAd007680; Tue, 18 May 2004 03:12:36 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.homeunix.com (8.12.10/8.12.10/Submit) id i4IACaYb007679; Tue, 18 May 2004 03:12:36 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Date: Tue, 18 May 2004 03:12:36 -0700 From: David Schultz To: Don Lewis Message-ID: <20040518101236.GB7186@VARK.homeunix.com> Mail-Followup-To: Don Lewis , Nikita@Namesys.COM, freebsd-fs@FreeBSD.ORG, mi+mx@aldan.algebra.com References: <16552.64697.572176.262372@laputa.namesys.com> <200405180428.i4I4SH7E019389@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200405180428.i4I4SH7E019389@gw.catspoiler.org> cc: freebsd-fs@FreeBSD.ORG cc: Nikita@Namesys.COM cc: mi+mx@aldan.algebra.com Subject: Re: QMail and SoftUpdates X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2004 10:13:40 -0000 On Mon, May 17, 2004, Don Lewis wrote: > Based on the information I found using Google, it appears that qmail > relies on link(2) being synchronous to let it know that a queued message > is safely on the disk with a known file name before it issues the "250" > response. I believe this was true without softupdates, but with > softupdates enabled it is definitely not true. If this is true, it's a boog in qmail[1]. The link(2) syscall guarantees atomicity, but not durability. This is why fsync(2) exists. [1] I would call it a ``bug'', but then I would be uttering one of the magic phrases to invoke djb in a public forum.