home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!europa.eng.gtefsd.com!howland.reston.ans.net!spool.mu.edu!agate!linus!philabs!crpmks!billb
- From: billb@crpmks.uucp (Bill Bochnik (Info Systems))
- Subject: Re: help: huge index file
- Reply-To: billb@crpmks.UUCP (Bill Bochnik (Info Systems))
- Organization: Ciba-Geigy Corporation
- Date: Thu, 28 Jan 1993 15:41:15 GMT
- Message-ID: <1993Jan28.154115.804@crpmks.uucp>
- References: <26JAN199310483026@vtpwr2.psl.ee.vt.edu> <1k7e7vINNn40@gap.caltech.edu>
- Lines: 43
-
- In article <1k7e7vINNn40@gap.caltech.edu> carl@SOL1.GPS.CALTECH.EDU writes:
- >In article <26JAN199310483026@vtpwr2.psl.ee.vt.edu>, gharpure@vtpwr2.psl.ee.vt.edu (VASUDEV GHARPURE) writes:
- >>
- >> We have a vax cluster, with a VS3100/76 as the boot node,
- >>running VMS 5.4-2. The boot node has a 1.0 GB external disk, used for
- >>user files.
- >>
- >> I used this disk as a temprory storage for a large number of
- >>files, which have since been deleted. But I am left with a huge index
- >>file (about 31K blocks). The original file was about 5K blocks.
- >>
- >> How do I get the index file back to normal? What harm does it do
- >>if it stays as it is?
- >
- >To get it back to a smaller size, you do a BACKUP, INITIALIZE, and restore of
- >the disk. As to what harm it does, it takes up an extra 26K blocks on your
- >disk. Unless you're really short of disk space, there's no need to do anything
- >about it.
- >--------------------------------------------------------------------------------
- >Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
- >
- >Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
- >understanding of astronomy is purely at the amateur level (or below). So
- >unless what I'm saying is directly related to VAX/VMS, don't hold me or my
- >organization responsible for it. If it IS related to VAX/VMS, you can try to
- >hold me responsible for it, but my organization had nothing to do with it.
-
- You will want to check the number of extents of the file (dump/head
- disk:[000000]indexf.sys). Too many will seriously affect performance.
-
- Map area
- Retrieval pointers
- Count: 6 LBN: 0
- Count: 3 LBN: 966
- Count: 3 LBN: 1201353
- Count: 13074 LBN: 1188279
- Checksum: 22283
-
- --
- Bill Bochnik | It's hard to be a James Bond in an Abbott
- Systems Analyst | and Costello world.
- Ciba-Geigy Corporation | Signed and sealed, they deliver oblivion.
- philabs!crpmks!billb | It's worse than that, he's dead Jim.
-