home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!europa.eng.gtefsd.com!paladin.american.edu!howland.reston.ans.net!spool.mu.edu!agate!stanford.edu!rock!concert!ais.com!bruce
- From: bruce@ais.com (Bruce C. Wright)
- Newsgroups: comp.os.vms
- Subject: Re: help: huge index file
- Message-ID: <1993Jan27.233611.5972@ais.com>
- Date: 27 Jan 93 23:36:11 GMT
- References: <26JAN199310483026@vtpwr2.psl.ee.vt.edu>
- Organization: Applied Information Systems, Chapel Hill, NC
- Lines: 26
-
- 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?
-
- There's no supported way to truncate the index file once it's grown
- like that. The usual approach is to do a backup and restore from tape.
-
- The main harm that the index file does if it stays that big is take
- up space. You _may_ slightly decrease performance if the index file
- is fragmented and breaks up the disk so that many user files become
- fragmented; since you're not using the file headers in the `higher'
- blocks in the index file, you won't get much of a performance hit from
- disk accesses to a fragmented index file. Few disk defragmenter
- programs will deal with a fragmented index file; again, the most
- common cure is to do a backup and restore from tape.
-
- Bruce C. Wright
-