🚀 go-pugleaf

There are a couple places where storage seems to mysteriously disappear.
The first place (aside from formatting losses) is the the VTOC (Volume
Table Of Contents?).  The total size shown in a LVOLFS takes into
account formatting losses, but not the VTOC.  This is around 5% or so,
and depends in part on the parameters used in involing the disk.

There is also file space which is not catalogued and thus is not "user
visible".  Most of this hangs around only for the duration of a process
(transcripts, process paging, etc.)  and should not be a long term
effect, although for a given task this can be a problem.

Other common things to watch out for is excessive use of the EDACL
command (which creates a new ACL object each time; edacling an entire
tree with 10K objects using 10MB!).  Use ACL to assign ACLs (EDACLing
only a "template") and/or use SALACL to merge ACL structures.  If you
have processes which die horribly on a frequent basis a FIND_ORPHANS
might help.

The above explain only where disk space "disappears" to.  These are
things to watch out for, but won't cause disk space to be 'found' on
rebooting.  A little is normal (if you SALVOL, the amount you get is a
meg or two lower than what the node will show you booted) but we have
never seen (unexplained) loss of free space (Our site has 40+ Apollos of
almost every type).  If I had to guess (and this is ONLY a guess) you
may have an application which is creating uncatalogued permanent
objects.  Does the disk space reappear with a boot only, or with a
SALVOL/boot combination only?  If the latter, look at the SALVOL report
and see if it tells you anything.

HI-MULTICS

"Disclaimer:  My employer doesn't believe a word I say"