From owner-freebsd-hardware Fri Jul 26 14:35:46 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA00123 for hardware-outgoing; Fri, 26 Jul 1996 14:35:46 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA00115 for ; Fri, 26 Jul 1996 14:35:44 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.7.3) with ESMTP id OAA00472 for ; Fri, 26 Jul 1996 14:34:59 -0700 (PDT) Message-Id: <199607262134.OAA00472@austin.polstra.com> To: freebsd-hardware@freebsd.org Subject: Which inode contains a given bad block? Date: Fri, 26 Jul 1996 14:34:59 -0700 From: John Polstra Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yesterday, I had to clean up a couple of bad blocks in my /usr filesystem. Is there a utility that will help me to figure out which inodes, if any, contained the bad blocks? In the olden days, this used to be possible, with icheck's "-b" option. Unfortunately, icheck has been replaced by fsck, which doesn't have that functionality. Short of writing a program myself, is there a way to do it under FreeBSD? Thanks, John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth