Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1+some 2/3/84; site dual.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!cbosgd!ihnp4!dual!fair
From: fair@dual.UUCP (Erik E. Fair)
Newsgroups: net.unix-wizards
Subject: Re: Correlation of block # to filename
Message-ID: <647@dual.UUCP>
Date: Tue, 3-Jul-84 20:19:15 EDT
Article-I.D.: dual.647
Posted: Tue Jul  3 20:19:15 1984
Date-Received: Thu, 5-Jul-84 00:23:11 EDT
References: <133@pthya.UUCP>
Organization: Dual Systems, Berkeley, CA
Lines: 22

What you need to do, Kip, is get the logical block number first.
If all you have is the physical block number, you have to figure out
which filesystem it's part of (i.e. which logical device). Once you
do that you can do this:

	% icheck -b bn# bn# bn# ... /dev/rhp0a
	inode xxxx

	% ncheck -i xxxx /dev/rhp0a
	xxxxx /foo/bar/bletch

Icheck will waltz through the inodes looking for the inodes which claim
your bad block. When you have the inode number (or numbers in the 
unfortunate case of dups), you can get the names which reference those
inodes from ncheck, which waltzes down the directories to this end.
Clear?

	Erik E. Fair	ucbvax!fair	fair@ucb-arpa.ARPA

	dual!fair@Berkeley.ARPA
	{ihnp4,ucbvax,cbosgd,decwrl,amd70,fortune,zehntel}!dual!fair
	Dual Systems Corporation, Berkeley, California