[7935] in Athena Bugs
vax 7.3I: quota
daemon@ATHENA.MIT.EDU (carla@ATHENA.MIT.EDU)
Thu Aug 15 10:10:42 1991
From: carla@ATHENA.MIT.EDU
To: testers@ATHENA.MIT.EDU, bugs@ATHENA.MIT.EDU
Cc: carla@ATHENA.MIT.EDU, kcunning@ATHENA.MIT.EDU
Date: Thu, 15 Aug 91 10:10:54 EDT
System name: mickey-mouse
Type and version: CVAXSTAR 7.3I (1 update(s) to same version)
Display type: SM
Now that more people are starting to use the new release (and the sipb
locker is over quota), we're really starting to see the impact of
having quota report for all attached AFS volumes.
Is there no way to make it not report on volumes the user has nothing
to do with, other than having them attached? If not, do we really need
to change quota for this release, since we aren't moving users to AFS?
The problem with quota reporting for other attached NFS lockers occurs
less frequently (because it only happens if you have something
attached from a partition the user has a quota on) and is easier to
explain -- we can tell the user that his quota on that partition is
being reported for each attached locker on that partition. The numbers
and any warning message are accurate, even if the locker name is not.
In the case of the 7.3 quota and AFS volumes, though, it makes no
sense to warn every user that he is over quota on /mit/sipb when he
has no control over the usage.
If this does need to go into this release in its current form,
it needs to be very well documented in the User Release
Notes, which it is not currently.
Carla
