Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!ames!ucbcad!ucbvax!SDCSVAX.UCSD.EDU!gr66%sdcc12
From: gr66%sdcc12@SDCSVAX.UCSD.EDU
Newsgroups: mod.computers.vax
Subject: (none)
Message-ID: <8611262103.AA28689@sdcc12.UCSD.EDU>
Date: Wed, 26-Nov-86 16:03:14 EST
Article-I.D.: sdcc12.8611262103.AA28689
Posted: Wed Nov 26 16:03:14 1986
Date-Received: Thu, 27-Nov-86 08:58:20 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 30
Approved: info-vax@sri-kl.arpa

----------------------------------------------------------------------
Subject: file cleanup on MicroVAX VMS 4.2 (long)
Newsgroup: info-vax

Hi.
   In cleaning up user names and associated files and quotas on
our MicroVAX, I ran into a large file that I cannot get rid of.
After backing up and deleting all files belonging to a departed 
user [200,010], a $ SHO QUOTA  showed that [200,010] still had
4171 blocks in use.  Using the FILES program (that was posted to 
this newsgroup last summer) that
looks at indexf.sys on a disk, I found that an EDTWORK.TMP file
of 4169 blocks belonging to [200,010] still remained in
dua0:[000000].  Attempts to delete the file failed since VMS said
it didn't exist.  How can I get rid of the file?  I know its 
file id, size and directory location from the FILES program.
   Another related problem : indexf.sys files on our disks have
grown to quite large size (one is 17990 blocks although not many
files are on disk).   I assume that deleted files must still have
records left in indexf.sys as a sort of history mechanism 
(I have not checked to see whether our disks are set for erase on
delete but is this related?)  Is re-initializing the
disks the only way to start anew with indexf.sys files (and, 
going on a tangent now, does anyone have a program that uses the 'old'
indexf.sys records to retrieve deleted files?). 

thanks in advance,

steve
gr66%sdcc12@SDCSVAX.ARPA