Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

disk quota exceeded?

4 views
Skip to first unread message

j...@gnv.ifas.ufl.edu

unread,
Aug 8, 1991, 12:30:08 PM8/8/91
to
Does anybody know what could cause the following disk quota exceeded problem:

two disks: one is user and the other is utility. They are both disk quota
enabled. One directory, say log.dir, on the utility disk has World:rwe access
and owner=[1,4]. All files under [log] also has world:rwe and owner=[1,4].

Entry [1,4] in the quota file shows more quota still available
SYSMAN> diskquota sh [1,4]/dev=utility
%SYSMAN-I-QUOTA, disk quota statistics on device GNV$DUB11: --
Node GNV
UIC Usage Permanent Quota Overdraft Limit
[1,4] 1288158 1500000 100


Problem: when a nonprivilege user from the user disk (with planty disk quota
available to his account) tries to write something in utility:[log], he will
get following message:
-RMS-E-CRE, ACP file create failed
-SYSTEM-F-EXDISKQUOTA, disk quota exceeded

Help is appreciated.
Jennifer
j...@gnv.ifas.ufl.edu

KE...@slacvm.slac.stanford.edu

unread,
Aug 8, 1991, 5:33:31 PM8/8/91
to
In article <1991Aug8....@gnv.ifas.ufl.edu>, j...@gnv.ifas.ufl.edu says:
>
>Does anybody know what could cause the following disk quota exceeded problem:
>
>two disks: one is user and the other is utility. They are both disk quota
>enabled. One directory, say log.dir, on the utility disk has World:rwe access
>and owner=[1,4]. All files under [log] also has world:rwe and owner=[1,4].
>
[stuff deleted]

>
>Problem: when a nonprivilege user from the user disk (with planty disk quota
>available to his account) tries to write something in utility:[log], he will
>get following message:
>-RMS-E-CRE, ACP file create failed
>-SYSTEM-F-EXDISKQUOTA, disk quota exceeded

This is to be expected. Even though the directory utility:[log] has
been given world read/write priviledge, the files created by a user in that
directory get charged against the _user's_ disk quota on that disk. You
need to either give your users some reasonable amount of quota on that
disk, or think of some other scheme, perhaps using ACL's and identifiers,
to give your users write access to the [log] directory.

-Ken

Dr. Kenneth H. Fairfield | Internet: Fair...@Slacvx.Slac.Stanford.Edu
SLAC, P.O.Box 4349, MS 98 | DECnet: 45537::FAIRFIELD (45537=SLACVX)
Stanford, CA 94309 | BITNET Fairfield@Slacvx
----------------------------------------------------------------------------
These opinions are mine, not SLAC's, Stanford's, nor the DOE's...

j...@gnv.ifas.ufl.edu

unread,
Aug 8, 1991, 6:37:01 PM8/8/91
to
Thanks to all who responsed my early question about disk quota exceeded
problem.

One thing I didn't think I made myself clear in the question was that when
I said a nonprivileged user tries to write something in utility:[log], I
actually meant he tries to write something to an EXISTING FILE (which has
world:rwe) in utility:[log]. So he does not need any disk quota on the
utility disk.

I have fixed the problem by rebuilding the disk quota file although I didn't
have a clear explanation why that did it.

Jennifer

0 new messages