From owner-freebsd-stable Mon Jan 31 8:21: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 0D85E14DC9 for ; Mon, 31 Jan 2000 08:21:04 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id QAA00384; Mon, 31 Jan 2000 16:20:16 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000131020845.T13027@fw.wintelcom.net> Date: Mon, 31 Jan 2000 16:20:16 -0000 (GMT) From: "Steve O'Hara-Smith" To: Alfred Perlstein Subject: RE: More than just logging, Re: JFS Cc: freebsd-stable@FreeBSD.ORG, Tom , Gary Palmer Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why logging filesystems don't work: > > You generally (with the hardware available in PCs now) > can't tell the difference between: > > 1) loss of power (ok!) > 2) crash where the filesystem datastructures weren't corrupted (ok!) > 3) crash where the filesystem datastructures were corrupted (ouch) > 4) crash where the disk/bus got scrambled (ouch) Nice analysis. I have a vague memory (I can't seem to find the message in the archives) of somebody on -current talking about a proposal for a log device that emitted events from the filesystem. Something like that and a WORM might make a reliable logging filesystem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message