[781] in testers

home help back first fref pref prev next nref lref last post

Vax 7.0C Problems with quota

daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Thu May 17 11:03:28 1990

From: epeisach@ATHENA.MIT.EDU
Date: Thu, 17 May 90 11:02:55 -0400
To: testers@ATHENA.MIT.EDU

For this report - I have configured wombat with the new rpc.rcquotad
that jnrees sent in yesterday. I am al;so running the new quota program.

===========================================================================
1) Without mappings, quota returns the message of no mappings on host.
This is not a documented change in the man page. The man page states
that "Only the super-user may use the optional user or group argu-
     ment to view the limits of users other than himself."
Users are going to see the warning and not know what it means. If a use
loses his/her mapping, the message is not infomative as we have not yet
trained users to understand the filesystm->machine name mapping.
quota.ucb still works....

medusa% ./quota -v
Disk quotas for epeisach (uid 11211):
Filesystem                 Type  ID              usage  quota  limit    timeleft
Warning: no NFS mapping on host: wombat
/mit/groupquota            group a_staff          8811  20000  23999
/mit/groupquota            group source-access    1109   5000   5999

medusa% quota.ucb -v
Disk quotas for epeisach (uid 11211):
Filesystem     usage  quota  limit    timeleft  files  quota  limit    timeleft
/wombat/u3      3900 100000 100000                931   7600   7800

===========================================================================
2) One used to be able to specify a uid and avoid security. Useful if
consultants wanted to check a users quota. This no longer works.

This should work as I am looking up my self....
medusa% ./quota -v epeisach
Disk quotas for user epeisach (uid 11211):
Filesystem     usage  quota  limit    timeleft  files  quota  limit    timeleft

medusa# ./quota -v 11211
Disk quotas for user epeisach (uid 11211):
Filesystem     usage  quota  limit    timeleft  files  quota  limit    timeleft
medusa# quota.ucb -v 11211
Disk quotas for epeisach (uid 11211):
Filesystem     usage  quota  limit    timeleft  files  quota  limit    timeleft
/wombat/u3      3900 100000 100000                931   7600   7800
===========================================================================

3) Inode limits are not displayed...., nor is "timeleft" for that situation.

While in /wombat/u3:

medusa% touch foo7
medusa% touch foo8
touch: foo8: Disc quota exceeded
medusa% quota -v
Disk quotas for epeisach (uid 11211):
Filesystem                 Type  ID              usage  quota  limit    timeleft
/mit/groupquota            group a_staff          8811  20000  23999
/mit/groupquota            group source-access    1109   5000   5999
/wombat/u3                 user  epeisach         3900 100000 100000


Hey - I'm way under quota. My usage is 3900 with a limit 100000, what
happened?

medusa% quota.ucb -v
Disk quotas for epeisach (uid 11211):
Filesystem     usage  quota  limit    timeleft  files  quota  limit    timeleft
/wombat/u3      3900 100000 100000                939    900    940    7.0 days

Oh, I hit my hard limit on files....


This is not good. Either Moira will have to be modified to give
outrageous numbers for inode limits, or quota should deal.

===========================================================================
4) quota does not fall back on old rpc.quotad if rpc.rcquotad if it
doesn't exist.

All servers need to be updated top run rpc.rcquotad before release date.
I have not looked to see what happens on a server that runs an
rpc.rcquotad - what affects it would have if used on a machine without a
group quota filsystem kernel.


home help back first fref pref prev next nref lref last post