From owner-freebsd-fs Fri Jan 31 10:50:52 2003 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6841B37B401; Fri, 31 Jan 2003 10:50:51 -0800 (PST) Received: from host213-122-194-66.in-addr.btopenworld.com (host213-122-194-66.in-addr.btopenworld.com [213.122.194.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id A647C43F43; Fri, 31 Jan 2003 10:50:48 -0800 (PST) (envelope-from dsl@l8s.co.uk) Received: (from dsl@localhost) by snowdrop.l8s.co.uk (8.11.6/8.11.6) id h0VIt7o08765; Fri, 31 Jan 2003 18:55:07 GMT Date: Fri, 31 Jan 2003 18:55:07 +0000 From: David Laight To: Steve Byan Cc: phk@freebsd.org, freebsd-fs@freebsd.org, tech-kern@netbsd.org Subject: Re: DEV_B_SIZE Message-ID: <20030131185507.G1487@snowdrop.l8s.co.uk> References: <2903.1044033486@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from stephen_byan@maxtor.com on Fri, Jan 31, 2003 at 01:41:35PM -0500 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 > Really? fsck can recover from losing 4K bytes surrounding the last > metadata block written? The only metadata that matter are the inodes and (for ffs) the indirect blocks. You do really want the latter to be single disk blocks - many systems actually write them synchonously. The inode is (probably) only 128 bytes, losing an inode block will lose the other files. A journaling filesystem probably already has ways around this... David -- David Laight: david@l8s.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message