Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ames!sdcsvax!ucbvax!RITVAX.BITNET!AWPSYS
From: AWPSYS@RITVAX.BITNET
Newsgroups: comp.os.vms
Subject: RE: Diskquota and DIR/GRAND
Message-ID: <8707280859.AA29821@ucbvax.Berkeley.EDU>
Date: Tue, 28-Jul-87 04:59:50 EDT
Article-I.D.: ucbvax.8707280859.AA29821
Posted: Tue Jul 28 04:59:50 1987
Date-Received: Wed, 29-Jul-87 05:04:11 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 16

The quota  usage maintained by QUOTA.SYS also includes the ammount
allocated for each file header.  This is typically 1 block per file, but it
can grow if you have a large file header (long ACLs, fragmented files with
lots of extents and multivolume files are several things that can cause a
file header to extend beyond one block). This file header usage is not
reported by the DIRECTORY command causing the discrepency between
DIR/GRAND/SIZ=ALL and SHOW QUOTA.

On a related issue, There STILL seems to be a bug which causes disk
quotas to drift in a cluster environment. Has anyone else seen this?
It seems to happen most often when SYSPRV is involved with file
creation. I work arround this by running VERIFY frequently on our
cluster disks to correct the quotas.

Andrew W. Potter
Rochester Institute of Technology