home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ukma!darwin.sura.net!haven.umd.edu!umd5!bill.ab.umd.edu!bill
- From: bill@bill.ab.umd.edu (Bill Bame)
- Newsgroups: comp.os.vms
- Subject: Re: help: huge index file
- Message-ID: <18202@umd5.umd.edu>
- Date: 28 Jan 93 14:04:31 GMT
- References: <26JAN199310483026@vtpwr2.psl.ee.vt.edu>
- Sender: news@umd5.umd.edu
- Reply-To: bill@office.ab.umd.edu
- Followup-To: comp.os.vms
- Organization: M.I.E.M.S.S.
- Lines: 33
-
- In article <26JAN199310483026@vtpwr2.psl.ee.vt.edu>, gharpure@vtpwr2.psl.ee.vt.edu (VASUDEV GHARPURE) writes:
-
- >...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?
-
- $ init device-name volume-label
-
- Of course this will erase any files you have on the disk. Check the qualifiers
- for INIT, there are lots of things you can do to control the size of INDEXF.SYS
- if your situation warrants it.
-
- > What harm does it do if it stays as it is?
-
- None. It will grow again anyway as soon as you start filling the disk up
- again. Surely you can spare <2% of your total space for a lowly index file.
-
- >
- >Vasudev
- >gharpure@power.psl.ee.vt.edu
- >
-
- -Bill
-
- --
- --------------------------------------------------------------------------------
- William P. Bame | sneakernet: William P. Bame
- internet: bill@office.ab.umd.edu | M.I.E.M.S.S.
- bbame@achi1.ab.umd.edu | 22 South Greene Street
- AT&T : [Work] (410) 328-3062 | Baltimore, MD 21201
- CIS : 71620,425 | Room: T1R55
- --------------------------------------------------------------------------------
-