Xref: utzoo comp.sys.att:5506 unix-pc.general:2214
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ames!pacbell!att!ttrdc!ttrde!pfales
From: pfales@ttrde.UUCP (Peter Fales)
Newsgroups: comp.sys.att,unix-pc.general
Subject: Re: From blocks to files (on a UNIXpc)
Summary: Block number or inode number?
Message-ID: <849@ttrde.UUCP>
Date: 10 Feb 89 14:44:02 GMT
References: <462@manta.pha.pa.us> <1392@mtunb.ATT.COM>
Organization: AT&T, Skokie, IL
Lines: 32

In article <1392@mtunb.ATT.COM>, jcm@mtunb.ATT.COM (was-John McMillan) 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?
> 
> 
> A)  There are so many uses of BLOCK NUMBER (and representations thereof) I
>     will simply PRESUME you are referring to:
>     	A LOGICAL BLOCK # on an identified FILE-SYSTEM.
>     
>     For this case:
>     	As root, run:
>     		/etc/ncheck  -i  ####  -a  /dev/rfp###
>     	(per instructions in Section 1M).


Thanks for your posting John,  you had some good tips on file system 
repair to add to my bag of tricks, but I must disagree with the statement
above.  According to my manual, as well as empirical evidence the numbers
following "-i" are a list of inodes, not a list of logical blocks.

Consider that a large file will contain many blocks, but a file will never
have more than one inode.

I am not aware of any standard tools that will go from logical block
numbers to files, though I would love to be proved wrong.

-- 
Peter Fales			AT&T, Room 2F-217
				200 Park Plaza
UUCP:	...att!ttrde!pfales	Naperville, IL 60566
Domain: pfales@ttrde.att.com	work:	(312) 416-5357