Xref: utzoo comp.sys.att:5533 unix-pc.general:2230
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!rutgers!bpa!manta!brant
From: brant@manta.pha.pa.us (Brant Cheikes)
Newsgroups: comp.sys.att,unix-pc.general
Subject: Re: From blocks to files (on a UNIXpc)
Summary: bf posted to unix-pc.sources, and available by mail.
Message-ID: <467@manta.pha.pa.us>
Date: 13 Feb 89 19:24:45 GMT
References: <462@manta.pha.pa.us> <446@amanue.UUCP> <1398@mtunb.ATT.COM>
Reply-To: brant@manta.pha.pa.us (Brant Cheikes)
Organization: Soul of the Gnu Machine, Philadelphia
Lines: 18

In article <1398@mtunb.ATT.COM> jcm@mtunb.UUCP (was-John McMillan)
writes [re a program to find inodes from blocks]:
>There USED to be a program that did this:
>	icheck  -b  #B#  ...  #B#  FileSystem
>		-- produced a list of INODES which "Owned" those blocks.

The extended features of icheck (superblock repair and miscellaneous
consistency checks) are no longer necessary, since they were
incorporated into fsck.  However, I have written a utility called "bf"
that will perform the above-described icheck function---find the
inodes that "own" specified blocks.  Bf has been tested on a 3b1
(SVR2) only, and probably makes assumptions about the filesystem
structure.  Bf was just posted to unix-pc.sources, and e-mail copies
(it's short) are available upon request.
-- 
Brant Cheikes
University of Pennsylvania, Department of Computer and Information Science
brant@manta.pha.pa.us, brant@linc.cis.upenn.edu, bpa!manta!brant