OMOND@DHDEMBL5.BITNET (Roy Omond) (01/31/86)
Has anyone observed the following "problem" under VMS 4.2 ? Running ANALYZE/DISK shows *many* discrepancies between the actual usage of disk space and the usage according to quota. e.g. QUOTA.SYS indicates 48197 blocks used, actual use is 48183 blocks for [540,20] QUOTA.SYS indicates 39077 blocks used, actual use is 39057 blocks for [550,20] QUOTA.SYS indicates 15267 blocks used, actual use is 15261 blocks for [550,50] QUOTA.SYS indicates 18724 blocks used, actual use is 18717 blocks for [550,60] QUOTA.SYS indicates 81700 blocks used, actual use is 81601 blocks for [700,10] Sometimes the difference can be pretty big; I have seen differences of several thousand blocks. I have the disks mounted with a quota cache size of 100, and write-through caching enabled. I asked around other Vax sites here, and each and every one had the same thing (750's, 780's, 785's, 8600's clustered and non-clustered). Running DISKQUOTA REBUILD corrects the quotas, but soon thereafter (couple of days), they start to depart from the "true" value again. I'd be interested to hear if this is as common as I suspect ... DEC Munich did not know of any problem nor could they reconstruct it. Any solutions ? Roy Omond (European Molecular Biology Laboratory, Heidelberg)
info-vax@ucbvax.UUCP (02/05/86)
We have noticed the same thing. I began to wonder what our users had been doing lately! So the problem is not confined to your site. I cannot offer any advice though - we just ignore it, as we run analyse/disk/repair regularly anyway and fix it.
#D15@DDATHD21.BITNET (02/06/86)
Hallo,
TSC MUNICH should know the Diskquota-discrepancy problem since
the middle of 1985. We discovered the same problem when we switched
from 3.7 to 4.1 last year and reported immediately to TSC-Munich
(never got an answer).
Our solution: $SET VOLUME/REBUILD at every startup.
With kind regards
Martin Knoblauch
Dept. for physical chemistry, PC 1
TH-Darmstadt, Petersenstr. 20, D6100 Darmstadt, West-Germany
BITNET: <#D15@DDATHD21.BITNET>