[BlueOnyx:15741] Re: No GUI changes can be made

[Michael Stauber]

Hi Dirk,

> having a little trouble with a 5107R: No GUI changes can be made.
> 
> When change disk space for a user, GUI says: Disk Quota cannot be set
> 
> I restarted cced, admserv but no effect.
> 
> Does anyone has an idea?

I just looked at it and fixed it. I emailed the details of my findings
to Uwe. My apologies that I couldn't look at it sooner.

Just for the record: Here are some useful steps to debug quota issues on
BlueOnyx VPS's on OpenVZ:

1a.) Make sure quota is enabled for the VPS. Just to be sure you can run
this command on the command line of the node:

vzctl set <VEID> --quotatime 0 --quotaugidlimit 1000 --save

Then restart the VPS to make sure the changes are put into effect.

1b.) *Only* use this step if you got to step #2 and things *still*
didn't work:

On the master node run this steps:

vzctl stop <VEID>
vzquota drop <VEID>
vzctl start <VEID>

That will drop the quota database that OpenVZ keeps for the VPS in
question. You can only do so when the VPS is stopped. On the restart of
the VPS the missing quota database will be rebuilt from scratch. The
restart of the VPS will therefore take considerably longer than usual.
Sit this one out and wait until it is finished. Then continue with step
#2 (and all others after it) as before.

2.) Run "repquota -a" inside the VPS. It *should* show a list of users
and groups. If it does, quota works. If you get error messages about
quota not being enabled or problems with /dev/simfs, then you can stop
right here and need to go back to step #1b.

3.) Inside the VPS pick a user and a group and check their quota
settings. Do not use system users for that (root or admin), as they have
unlimited quota anyway. So pick a Vsite user instead:

quota -s -g site1
quota -s -u <username>

That should show how many MB this group and this user are allowed to
use. If it doesn't show anything, reports "unlimited" (or "0"), then
quota information is not available, even though quota itself is running.
We fix that in the next step:

4.) Run /usr/sausalito/sbin/disk_restorequotas.pl as root inside the
VPS. It will read the quota allowances of sites and users from CODB and
will publish it to the quota database of the filesystem.

5.) Run /usr/sbin/swatch as "root" inside the VPS. It will read how much
disk space users and group are currently using and will update that
information into CODB.

These five steps allow you to check the quota functionality for correct
behavior and allow you to repair the VPS disk quota if it's broken.

-- 
With best regards

Michael Stauber