From owner-freebsd-stable Sat May 5 5:54:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 1950037B422 for ; Sat, 5 May 2001 05:54:45 -0700 (PDT) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id FAA14268 for ; Sat, 5 May 2001 05:54:38 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda14266; Sat May 5 05:54:19 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f45CsDt49662 for ; Sat, 5 May 2001 05:54:13 -0700 (PDT) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdQ49660; Sat May 5 05:53:17 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.3/8.9.1) id f45CrHW01020 for ; Sat, 5 May 2001 05:53:17 -0700 (PDT) Message-Id: <200105051253.f45CrHW01020@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdKC1015; Sat May 5 05:52:51 2001 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: stable Subject: Re: soft update should be default In-reply-to: Your message of "Sat, 05 May 2001 00:58:39 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 May 2001 05:52:51 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Go rdon Tetlow writes: > On Fri, 4 May 2001, Nick Sayer wrote: > > > Mike Smith wrote: > > > > >> Hi, > > >> > > >> Why 'soft update' is not default? > > >> It adds performance and stability, doesn't it? > > > > > > > > > It requires disabling of write caching, which typically reduces > > > performance (significantly). > > > > > Why wouldn't a similar requirement (disabling write caching) apply to > > non-softupdates filesystems? The disk doesn't know whether the write is > > synchronous or not, after all. > > That's the thing about it. If you have write-caching enabled then all bets > are off in any case (ie, you might as well run in async). In addition, > soft updates does some really smart things even over async. I sense (maybe incorrectly, so forgive me if I sense wrong) that people think that w/o softupdates turned on that FreeBSD performs sync writes. By default the *BSDs perform synchronous metadata (SMD) writes. That means that metadata, e.g. inode and directory writes are synchronously written, while the data itself is asynchronously written. Softupdates orders the metadata writes in such a manner that batches of metadata writes, each batch being synchronously written, are asynchronously written out. The data itself, e.g. user data, is asynchronously written out when SMD or softupdates is used. If you have a critical database, it is no more protected by softupdates than SMD. In that case a DBMS would need to issue fsync() after each commit or the filesystem would have to be mounted synchronously. Of course as Gordon writes above, all bets are off if your disk does write-caching. There is an excellent paper entitled, Soft Updates: A Solution to the Metadata Update Problem in File Systems, by Gergory R. Granger and Yale N. Patt at EECS, University of Michigan. The paper is at http://www.ece.cmu.edu/~ganger/papers/CSE-TR-254-95/. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message