Xref: utzoo comp.unix.i386:3111 comp.unix.wizards:20710
Path: utzoo!attcan!uunet!dino!ux1.cso.uiuc.edu!uicsrd.csrd.uiuc.edu!bruner
From: bruner@uicsrd.csrd.uiuc.edu (John Bruner)
Newsgroups: comp.unix.i386,comp.unix.wizards
Subject: Re: Can I derive an inode # from an absolute sector #?
Summary: use icheck
Message-ID: <1990Feb22.144412.11485@ux1.cso.uiuc.edu>
Date: 22 Feb 90 14:44:12 GMT
References: <24@hite386.UUCP>
Sender: news@ux1.cso.uiuc.edu (News)
Reply-To: bruner@uicsrd.csrd.uiuc.edu (John Bruner)
Organization: CSRD, UIUC
Lines: 31

In article <24@hite386.UUCP> steve@hite386.UUCP (Steve Hite) writes:
>    I have 386/ix v2.0.2.  Recently, I had gotten an absolute sector read
>error report.  I have called Interactive tech support about this in the past
>and they couldn't tell me explicitly how to find out the inode # if there
>is a disk error giving the absolute sector # as the problem spot on the hard
>disk.  Can it be done?  How? ...

The old filesystem consistency program "icheck" will do what you want.
Vendors often provide icheck/dcheck/ncheck with their ports (particularly
V7-derived ones like BSD, SunOS, etc.)  If Interactive supplied it, you
can get the inode number with the command:

	icheck -b blockno device

where "blockno" is the block number within device "device".  Use the
raw device if possible.

You can get the filenames which reference this inode (the (hard) links
to the file) with "ncheck":

	ncheck -i inode device

Again, use the raw device and be prepared to wait a while if the
filesystem is large.

Both of these commands are safe to use while the filesystem is mounted,
although given the device errors I probably would do it in single-user
mode with the filesystem unmounted.
--
John Bruner	Center for Supercomputing R&D, University of Illinois
	bruner@uicsrd.csrd.uiuc.edu	(217) 244-4476