Xref: utzoo comp.sys.att:5529 unix-pc.general:2228
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!rutgers!att!mtunb!jcm
From: jcm@mtunb.ATT.COM (was-John McMillan)
Newsgroups: comp.sys.att,unix-pc.general
Subject: Re: From blocks to files (on a UNIXpc)
Message-ID: <1398@mtunb.ATT.COM>
Date: 13 Feb 89 16:32:31 GMT
References: <462@manta.pha.pa.us> <446@amanue.UUCP>
Reply-To: jcm@mtunb.UUCP (was-John McMillan)
Organization: AT&T ISL Middletown NJ USA
Lines: 36

Mea culpa:  too many balls in the air, too few brains in the head.
I indeed posted erroneous advice.  Read on....

In article <446@amanue.UUCP> jr@amanue.UUCP (Jim Rosenberg) writes:
>In article <462@manta.pha.pa.us> brant@manta.pha.pa.us (Brant Cheikes) writes:
>>Given a block number, how can I find out (a) if it's part of a file,
>>and (b) what file it's part of?
>>...
>This is something that people wanna do so often it amazes me there's not a
>utility for this.  An fsdb wizard might be able to tell you how -- a script
>redirecting fsdb's input???

There USED to be a program that did this:

	icheck  -b  #B#  ...  #B#  FileSystem
		-- produced a list of INODES which "Owned" those blocks.

(Unfortunately, I forgot to post the above in my previous, brain-damaged note.)
The next step is to use ICHECK's output:

	ncheck  -i  #I#  ...  #I#  FileSystem
		-- then turned those INODE numbers into FileNames.

When FSCK came along, AT&T seems to have dropped ICHECK.  I can't legitimately
hand out any hack I have for icheck... but others are apparently busily
at work on it.

Written properly, an "icheck" clone could be run as:
	ncheck -i `eyecheck -b #B# ... FS 2> Aye2` FS

Berkeley still provides ICHECK, I believe -- probably DCHECK as well.
Ahhhh, those beautiful red-eyed nights spent with *check, piecing
together blithered FS before FSCK was born.

jc mcmillan	-- att!mtunb!jcm	-- speaking for self, only
				(Those WEREN'T the "good ol' days", were they?)