🚀 go-pugleaf

Stephen,

We are running VMS 4.4 on our cluster.
It still has bugs in the disk file quota software.

We have seen quotas wrong by several thousand blocks, particularly
after having done a complete "cluster shutdown" and reboot.

We have also found files that have been assigned the wrong owner.
You'll need to get a directory of the entire disk to find these.

1. You can correct the file owner field by specifying
"SET FILE/OWNER=correct_name file.ext", which usually will update the
disk quota file appropriately. There are certain pathological
situations when this will cause quota checking to be disabled on
the volume.

(It happened to me when I had restored a large number of files for
someone without specifying /OWNER=ORIGINAL. As  a result, the files
all belonged to "system". It also would have put him way over quota.
I did the SET FILE to put the ownership right, and then realized that
I had to update his diskquota entry. It claimed that quotas weren't
enabled for the volume, although they had been. Fortunately ENABLE worked.)

2. You can try running DISKQUOTA and specifying "REBUILD".
This can be done while the system is still up.
All other file i/o to that volume will hang until DISKQUOTA finishes.

3. You may need to take the system stand-alone and run
ANALYZE/DISK/REPAIR to get it straightened out.

I hope this helps.

Selden E. Ball, Jr.
(Wilson Lab's network and system manager)

Cornell University                 NYNEX: +1-607-255-0688
Laboratory of Nuclear Studies     BITNET: SYSTEM@CRNLNS
Wilson Synchrotron Lab              ARPA: SYSTEM%CRNLNS.BITNET@WISCVM.WISC.EDU
Judd Falls & Dryden Road          PHYSnet/HEPnet/SPAN:
Ithaca, NY, USA  14853             LNS61::SYSTEM = 44283::SYSTEM (node 43.251)