home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!van-bc!rsoft!agate!ames!decwrl!deccrl!bloom-beacon!eru.mt.luth.se!lunic!sunic!mcsun!uknet!miclon!nreadwin
- From: nreadwin@micrognosis.co.uk (Neil Readwin)
- Newsgroups: comp.os.vms
- Subject: Re: LBN => Filename / FID => Filename ??
- Keywords: lbn, fid, indexf.sys
- Message-ID: <1992Aug19.110649.26298@micrognosis.co.uk>
- Date: 19 Aug 92 11:06:49 GMT
- References: <1992Aug17.165506.21539@oracle.pnl.gov>
- Sender: news@micrognosis.co.uk (News account)
- Organization: Micrognosis, London, UK.
- Lines: 25
-
- In article <1992Aug17.165506.21539@oracle.pnl.gov>, David Cowley writes:
- |> Does anyone have a way to take a logical block number (LBN) and determine
- |> which file it's part of? [...] The same goes for the File IDs (e.g.
- |> (135,1,0) ) reported by utilities like ANALYZE/DISK.
-
- I can't help with LBNs, but FIDs are easier. The following piece of DCL will
- dump out the file header. That contains a file name and you can follow back
- the 'back link file identification' to get the complete spec.
-
- $ write sys$output "Enter device name ..."
- $ read sys$command device
- $ write sys$output "Enter FID (eg 1235,1,1) ..."
- $ read sys$command the_fid
- $!
- $ the_block = 4*F$GETDVI(device, "CLUSTER") + -
- ((F$GETDVI(device, "MAXFILES") + 4095) / 4096) + -
- (f$element(2, ",", the_fid) / 256) * 65536 + -
- f$element(0, ",", the_fid)
- $ dump /file /block=(count=1,start='the_block') 'device':[000000]INDEXF.SYS
-
- If you want to get into this stuff then you need "VMS File System Internals"
- by Kirby McCoy (EY-F575E-DP, ISBNs 1-55558-056-4 and 0-13-931783-X).
- --
- Phone: +44 71 528 8282 E-mail: nreadwin@micrognosis.co.uk
- Anything is a cause for sorrow that my mind or body has made
-