From owner-freebsd-fs Fri Mar 8 19:30:46 2002 Delivered-To: freebsd-fs@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 0618437B400; Fri, 8 Mar 2002 19:30:45 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id DCB0CAE23A; Fri, 8 Mar 2002 19:30:44 -0800 (PST) Date: Fri, 8 Mar 2002 19:30:44 -0800 From: Alfred Perlstein To: mckusick@freebsd.org Cc: fs@freebsd.org Subject: softupdates durability enhancement? Message-ID: <20020309033044.GC26621@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org People were complaining about crashes after softupdates giving them truncated files after reboot. I know from your earlier posts that this is actually more a bug in the way editors are prone to write out files than a real softupdates bug, I would also expect most logging filesystems to potentially have the same problem. One way to potentially reduce the chances of this are to more aggressively push out softdeps when the backlog is short. Meaning that when the softdep clock is nearly empty you push things out faster and as the clock fills with dependancies you begin to delay them up until the point you are forced to begin sync'ing them. The idea is for workstation loads where people are editing single files you reduce the window of having the file at zero length and thereby you protect them a bit more against stupid editors that do unsafe/non-transactionalsafe in-place updates. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message