From owner-freebsd-isp Mon Aug 26 11:31:13 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA00990 for isp-outgoing; Mon, 26 Aug 1996 11:31:13 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA00985 for ; Mon, 26 Aug 1996 11:31:10 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30 † id LAA12478; Mon, 26 Aug 1996 11:31:06 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id LAA16588; Mon, 26 Aug 1996 11:30:49 -0700 (PDT) Message-Id: <199608261830.LAA16588@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Joe Greco cc: michael@memra.com, freebsd-isp@freebsd.org, craigs@os.com Subject: Re: Anyone using ccd (FreeBSD disk striper) for news In-reply-to: Your message of Mon, 26 Aug 96 12:45:04 -0500. <199608261745.MAA00687@brasil.moneng.mei.com> Date: Mon, 26 Aug 1996 11:30:49 -0700 From: "Michael L. VanLoon" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >> And did you need to fo that tweak to UFS meta data updates that makes it >> >> more like Linux's ext2fs? >> >I've played with metadata updates before (disabled ATIME and MTIME updates) >> >but I don't want to do it on a production system until there is an >> >officially sanctioned method to do so. >> On the other hand, I've had two NetBSD machines running with all >> filesystems in async mode for several months, now. One of these >But async mode will not buy you much in this case...! Async is simply >delaying the inevitable, which is already delayed in FreeBSD until the next >30-second sync. I do not want to write metadata at _all_ if all it is is >an ATIME update... if I have to write it, now OR later, I am losing >bandwidth and transactions per second that I would rather spend reading >other data. Not completely. What if the data that is being postponed changes two or three times while it's in the cache. When it finally gets written, you just wrote once what would have been written two or three more times. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... -----------------------------------------------------------------------------