[8033] in Athena Bugs
Re: vax 7.3L: quota -v
daemon@ATHENA.MIT.EDU (Richard Basch)
Sat Aug 24 22:57:08 1991
Date: Sat, 24 Aug 91 22:57:29 -0400
To: jasper@MIT.EDU
Cc: bugs@MIT.EDU
In-Reply-To: Asper Argo's message of Sat, 24 Aug 91 18:28:35 EDT,
From: "Richard Basch" <basch@MIT.EDU>
Disk quotas for jasper (uid 9552):
Filesystem Type ID usage quota limit files quota limit
/mit/jasper user jasper 788 1200 1440 97 600 720
/mit/bitbucket user jasper 3770 2500 75000<< 39 2000 20000
/srvd volume 102788 110000 110000
User jasper over disk quota on /mit/bitbucket, remove 1271K within 4.0 days
What should have happened:
I do not understand the /srvd line. What does it mean?
The rest is as it should be.
In 7.3, there is more support for AFS filesystems. One of the things
that was lacking was the reporting of quotas on AFS filesystems. Under
AFS, quotas are associated with the "locker", not with a user. Whether
a user can write to the "locker" or not is determined by other
"mechanisms" which are impossible to determine (the user can have access
to portions of the "locker" and be restricted from other sections).
It turns out that the system you were logged into was using AFS for
delivering the system packs. The quota associated with the AFS "volume"
that was mounted on /srvd was 110MB, of which 103MB of it was used.
Naturally, the system software is writable only to a few people, so the
quota reported is that of the people putting the release together.
AFS allows for finer-grained access control than NFS, allowing multiple
people to have administrative and write access to directories, and it is
on a per-directory basis, so it is difficult to determine if you had any
write access to any part of that tree. There are several AFS
filesystems that have differing protections on the top-level directory
and its subdirectories, so no heuristic algorithm will work well.
The "-v" option means report any type of quota restriction about all
mounted filesystems. However, the summary warnings that are generated
are generally associated with the user. If a filesystem is mounted
read-write by the user, it is more likely to be one that the user can
modify. (/srvd is a read-only filesystem and was mounted by root, so
even if it were over quota, you would not get a warning.) Below is an
excerpt of the quota(1) man page from the new release. I have put
highlights in the right margin where it describes about AFS...
DESCRIPTION
Quota displays users' and groups' disk usage and limits on <<<
local and NFS mounted file systems, as well as AFS lockers <<<
that have been attached. If a user or group is specified <<<
(by name or by id), quota will return information on disk
usage and limits for the given user or group (See PERMIS-
SIONS below).
Quota without options displays only warnings about mounted
file systems where usage is over quota. As a special case, <<<
the user will only be warned about AFS lockers if the user <<<
attached the locker, and the mode it was attached with was <<<
'w'. This is done to try to reduce the number of lockers <<<
the user is warned about that they have no control over. <<<
OPTIONS
-v This option will display usages and limits for the user
and any groups the user is a member of on all local and
NFS mounted file systems where quotas exist, in the
following format:
Disk quotas for joeuser (uid 12345):
Filesystem Type ID usage quota limit files quota limit
/mit/joeuser user joeuser 2394 2000 2400<< 313 1000 1200
User joeuser over disk quota on /mit/joeuser, remove 395K within 7.0 days
Additionally, it will display quota information for any <<<
AFS lockers that have been attached. On NFS or local <<<
file systems, everyone has a "soft" limit for disk
space usage (given in the first quota column) and a
"hard" limit (given in the first limit column). The
amount of space currently in use is shown in the usage
column. These values are measured in kilobytes (1024
characters).
I hope this explanation helps.
If you have any suggestions for improvement, we would be glad to hear
them. (Personally, I think the man page needs some editing, still...)
-Richard Basch
Athena Systems Development
