[comp.os.vms] diskquota ...

burris%luxor.DECnet@LLL-ICDC.ARPA ("LUXOR::BURRIS") (07/20/87)

	Has anyone run into a problem with diskquota? We have a 750 with
one 300mb drive that has one particular account which receives the following
message: "ACP file create failed - Diskquota exceeded". In looking at the
account with the diskquota show command, I see 40000/100 blocks allocated,
with 22000 in use. Increasing this amount to 50000/300 had no beneficial
effect, nor did a rebuild command help. The only band-aid I've been able
to find at this point is to issue the account the "exquota" privledge.
Virtually any file operation with this account causes the above msg.
	Thanks in advance:	Keith Burris
				LLNL ms-L-865
				P.O. Box 808
				Livermore, Ca. 94550 (415)423-5566
------

graham@DRCVAX.ARPA (07/20/87)

There are a couple of items to check:

Have you recently done a REBUILD on the disk quota file.  This is a good 
thing to do on a semi-regular basis; it seems that diskquota gets confused 
occasionally.

There are many different things that could cause the message you mentioned. 
What exactly was the operation that elicited this message?  If another 
porcess was involved, perhaps that process's diskquota was inadequate.


Just some thoughts for your perusal.

Dan Graham
GRAHAM@DRCVAX.ARPA
------

ANK@CUNYVMS1.BITNET (08/05/87)

>In addition to the quotas showing a small random-walk variation,
>sometimes large files are created with the wrong owner.
>They appear in the intended directory, but the owner field contains
>somebody else's uic. The incorrect uic is always one defined on our
>system, so it's not entirely random.

You have to first check if the user who created the files has privs
such as SYSPRV ? It allows user to create files with either his/her
UIC or that of another UIC. Since it is possible also that the
intended directory could have RWED to group or world may allow
different users to write files into it. A common phenomenon in some
directories at our site (We also run EUNICE which as /tmp writable
and also /usr too...which as all too-corruptible bin files also )

A workble solution is to prevent group either W or D access to all
but their own and provide ACL controls to directories that need to
be shared by users from different groups ....

                                                Anil Khullar
                                        {Ph.D. Prog in Psychology
                                         C.U.N.Y. Grad. Center.
                                        33 W 42 St. Box 295,
                                         New York NY 10036      }

BITNET:ank@cunyvms1
INTERNET:ank%cunyvms1.BITNET@wiscvm.edu
==========================================================================
ON THE SEVENTH DAY GOD RESTED AND WATCHED CELTICS PLAY AT THE GARDEN
==========================================================================
[DISCLAIMER: They say after Boston there is heaven, I agree; I say after
LispM there is nirvana, they don't. This and other such opinion are
held dearly by me, my employers and the institution I represent do not
necessarily hold that view. I am sole culprit of such fantasies. No living
being is responsible, however unsolicited support is welcome]