I won't include my entire query but basically df was returning bad data,
and quotas were getting "fixed" to 0 and other bad values. One of things I
had recently done was:
> -- run vquotacheck (and quotacheck -- but they are the same?)
> the first few times I ran this it seemed great -- fixed up a problem
> with a student whose usage was about 3MB but who the quota system
> thought was using 20MB. I just ran it now, and it's fixing people's
> usages to 0. I first ran this program on friday, 11/10/96 (10/11/96 in
> US usage).
This was the cause of my problems.
The problem seems to be cause by running a command like:
# vquotacheck -guv -a
I have just run vquotacheck on the filesets individually and things look better:
6# df
Filesystem 1024-bl Used Availab Capa Mounted
root_domain#root 98304 78609 13400 86% /
/proc 0 0 0 100% /proc
usr_domain#usr 861184 508071 336744 61% /usr
tmp_dmn#tmp_fs 200200 7 192016 1% /tmp
r0_dmn#grad_fs 2064384 1808702 40584 98% /users/studs/grad
r0_dmn#ugrad_fs 2064384 2160502 0 105% /users/studs/ugrad
r1_dmn#ass_fs 2064384 1274701 789683 62% /ass
r1_dmn#staffc_fs 2065408 1690049 375359 82% /users/staffc
r2_dmn#grada_fs 2064384 1692030 372354 82% /users/studs/grada
r2_dmn#foo 2064384 782865 1281519 38% /foo
gradb_dmn#gradb_fs 895048 545630 331208 63% /users/studs/gradb
These are numbers I can believe.
Thanks to:
Robin Kundert <rkundert_at_paul.spu.edu>
(whose "me too" pointed me in the right direction)
Simon Amor <spa_at_dmu.ac.uk>
Kurt Carlson <SXKAC_at_orca.alaska.edu>
It would seem that df, and other commands that return values about filesets
(rather than file domains) use the quota information to determine the used
space in the fileset.
I'll make a bug report to DEC.
clare
--
Clare West, Rm 107, Ext 8266
clare_at_cs.auckland.ac.nz
Received on Fri Oct 25 1996 - 04:08:22 NZDT