From owner-freebsd-fs@FreeBSD.ORG Thu Aug 26 18:30:39 2004 Return-Path: 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 B671616A4CE for ; Thu, 26 Aug 2004 18:30:39 +0000 (GMT) Received: from citi.umich.edu (citi.umich.edu [141.211.133.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D22443D1F for ; Thu, 26 Aug 2004 18:30:39 +0000 (GMT) (envelope-from rees@citi.umich.edu) Received: from citi.umich.edu (dumaguete.citi.umich.edu [141.211.133.51]) by citi.umich.edu (Postfix) with ESMTP id C21211BB71 for ; Thu, 26 Aug 2004 14:30:38 -0400 (EDT) To: freebsd-fs@freebsd.org From: Jim Rees In-Reply-To: Maxim Konovalov, Thu, 26 Aug 2004 21:56:15 +0400 Date: Thu, 26 Aug 2004 14:30:38 -0400 Sender: rees@citi.umich.edu Message-Id: <20040826183038.C21211BB71@citi.umich.edu> Subject: Re: problems with fsck_ffs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Aug 2004 18:30:39 -0000 There are src/tools/tools/find-sb and ports/sysutils/scan_ffs. And I have my own implemetation of course :-) Yes, but find-sb really should be part of fsck. And while we're on the subject, maybe newfs should have an upper limit on how many spares it generates. Or at least stop telling you the block number of each one. The days when a large shop might have one or two disk drives, and you would actually write down the block numbers of the spares, are long gone.