[Info-vax] FREESPADRIFT

[Kerry Main]

> -----Original Message-----
> From: Info-vax [mailto:info-vax-bounces at info-vax.com] On Behalf Of
> Phillip Helbig undress to reply via Info-vax
> Sent: 12-Jun-16 4:23 PM
> To: info-vax at info-vax.com
> Cc: Phillip Helbig undress to reply <helbig at asclothestro.multivax.de>
> Subject: Re: [New Info-vax] FREESPADRIFT
> 
> In article
> <mailman.301.1465761765.14919.info-vax_info-vax.com at info-vax.com>,
> Kerry
> Main <kerry.main at backtothefutureit.com> writes:
> 
> > > > What causes the free-space count to become wrong?  Since VMS
> > > obviously
> > > > knows about it (otherwise /REPAIR couldn't fix it), why isn't it
> always
> > > > correct?
> > > >
> > > > Is there any reason not to run ANA/DISK/REPAIR, say, once per
> day?
> 
> > $ Help set volume /rebuild
> 
> I do this once per day.  I don't think they do the same things (though
> there might be some overlap).
> 

They don't do the same thing, but if all you are worried about is free 
space values, then this should do it. From help file-

"Recovers caching limits for a volume that was dismounted
improperly. If a disk volume was dismounted improperly (such
as during a system failure), and was then remounted with the
MOUNT/NOREBUILD command, you can use SET VOLUME/REBUILD to
recover the caching that was in effect at the time of the
dismount. The FORCE option forces the disk to be rebuilt
unconditionally, thus updating the free block count in the disk
volume's lock value block."

Analyze /disk obviously does a lot more.

Regards,

Kerry Main
Kerry dot main at starkgaming dot com