From owner-freebsd-fs@FreeBSD.ORG Tue May 18 18:10:11 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 C791B16A4CE; Tue, 18 May 2004 18:10:11 -0700 (PDT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD99F43D3F; Tue, 18 May 2004 18:10:11 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc11) with ESMTP id <2004051901095801300a4c55e>; Wed, 19 May 2004 01:09:58 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id SAA46345; Tue, 18 May 2004 18:09:58 -0700 (PDT) Date: Tue, 18 May 2004 18:09:58 -0700 (PDT) From: Julian Elischer To: Mikhail Teterin In-Reply-To: <200405181931.59373@misha-mx.virtual-estates.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-fs@FreeBSD.org cc: Nikita@Namesys.COM cc: Don Lewis cc: lioux@FreeBSD.org 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: Wed, 19 May 2004 01:10:11 -0000 On Tue, 18 May 2004, Mikhail Teterin wrote: > =On Tue, 18 May 2004, Don Lewis wrote: > = > => On 18 May, Julian Elischer wrote: > => > > => > > =[...] > = > => > > => > An fsync will sync ALL directory entries pointing to the file > => > => I haven't looked at how qmail works, but my suspicion is that it > => fsync()s the file and then creates a link (and probably unlinks > => the old name) to mark the queue file as valid and is not partially > => written. I think this would work with softupdates if the file were > => fsync()ed again after the link() call. I won't comment about why this > => change is unlikely to make it into the code. > = > =a single fsync AFTER the link but before acking the mail would be > =sufficient. > > Should the mail/qmail port do that? it certainly could... > > -mi > >