I just discovered to my horror that my AdvFS filing systems were running
without quota enforcement, even though the fstab entries specify rw,userquota
(and/or group quotas, as appropriate). If I run "vquotaon -a" manually,
quotas are turned on correctly.
Naturally I expect this to happen by default.
There's a startup script /sbin/init.d/quota which turns on UFS quotas at
startup, but not AdvFS quotas.
I can't find anywhere that runs "vquotaon -a" at startup, so maybe the result
is not too surprising. But my real problem is that I am 90% sure that this
used to work - I'm sure I would have tested it, and if it had never worked, I
feel sure that I would have found more users exceeding their assigned quota
than I actually did.
In recent weeks I have upgraded from 3.2A via 3.2C to 3.2D-1, and also applied
a 3.2D-1 consolidated patch kit.
So, the questions for the list:
- Anybody else have the problem? (you can check the quota enforcement status
of with "showfsets").
- Am I right that it used to work but does no longer?
- How is it supposed to work? Surely I shouldn't have to hack the startup
scripts just to make quotas work, especially as the work is already done for
me for UFS filing systems.
Unless anybody points out that I'm doing something silly I will probably
tackle the support centre on this one. I've very annoyed about it because one
or two users have exceeded their assigned quota by an order of magnitude, and
once space is given, you can never get it back...
--
Martyn Johnson maj_at_cl.cam.ac.uk
University of Cambridge Computer Lab
Cambridge UK
Received on Wed Aug 14 1996 - 19:32:37 NZST