From owner-freebsd-hackers Tue Feb 6 9:53:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 7CB0D37B491 for ; Tue, 6 Feb 2001 09:52:42 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f16HoZD62214; Tue, 6 Feb 2001 09:50:35 -0800 (PST) (envelope-from dillon) Date: Tue, 6 Feb 2001 09:50:35 -0800 (PST) From: Matt Dillon Message-Id: <200102061750.f16HoZD62214@earth.backplane.com> To: Poul-Henning Kamp Cc: Charles Randall , Dan Phoenix , Alfred Perlstein , Jos Backus , freebsd-hackers@FreeBSD.ORG Subject: Re: soft updates and qmail (RE: qmail IO problems) References: <36088.981481432@critter> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> softupdates disk may wind up unwinding 'more' of the last few moments :> worth of operations then a normal filesystem would. And, I might add, :> Reiser is the same way. :> :> The only way to guarentee that file data is written to disk, with any :> filesystem no matter how it is mounted (even sync mounted filesystems), :> is by calling fsync(). :> :> So I would stick with softupdates. : :... provided that qmail calls fsync(2). : :-- :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 It doesn't matter whether qmail calls fsync or not as far as using softupdates goes. No filesytem will guarentee stable storage with fsync(), so softupdates is not going to be too much worse then other FS's. So one might as well use softupdates. When/if qmail gets its act together and calls fsync() properly, softupdates will guarentee a level of consistency that only ReiserFS or XFS can even come close to matching. A normal EXT2FS or FFS filesystem, even with fsync(), *EVEN* with synchronous mounts, cannot guarentee file consistency because it is still possible to corrupt the directory and loose the file that was fsync()'d if a crash were to occur just after the fsync(). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message