Difference between revisions of "Fixing Quota"
From Pulsed Media Wiki
(One intermediate revision by one other user not shown) | |||
Line 1: | Line 1: | ||
+ | Quota can have multiple types of problems. Here are the 2 most common situations. | ||
+ | |||
+ | == Skewed quota information == | ||
Occasionally quota data becomes skewed and requires a recheck. [[PM Software Stack]] includes automated script which does more than just rechecks the quota. | Occasionally quota data becomes skewed and requires a recheck. [[PM Software Stack]] includes automated script which does more than just rechecks the quota. | ||
+ | This includes user names not shown, wrong used amounts etc. | ||
Situations where this maybe necessary are and may fix: | Situations where this maybe necessary are and may fix: | ||
− | + | * Quotas show up as 0 (limits or used) | |
− | + | * Removed accounts still showing up on [[repquota]] | |
− | + | * Reported usage does not reflect reality (ie. shows more used for a user than actually is used) | |
− | + | * Accounts missing from report | |
cd /scripts/util | cd /scripts/util | ||
Line 13: | Line 17: | ||
After a while quota has been checked and new quota files have been created, and quota will be re-enabled automatically. | After a while quota has been checked and new quota files have been created, and quota will be re-enabled automatically. | ||
− | If you get write permission error, | + | If you get write permission error, see next section. |
+ | |||
+ | |||
+ | == Permission denied aquota.user for root == | ||
+ | So something went awry within kernel and even root does not have permission to these files? | ||
+ | |||
+ | Reboot server, then after rebooting login and issue following commands: | ||
− | rm -rf /home/aquota. | + | rm -rf /home/aquota*.new |
− | + | cd /scripts/util | |
./quotaFix.php | ./quotaFix.php | ||
+ | This ought to be fixed now. | ||
[[Category:PM Software Stack Guides]] | [[Category:PM Software Stack Guides]] | ||
[[Category:Guides]] | [[Category:Guides]] |
Latest revision as of 13:26, 22 May 2011
Quota can have multiple types of problems. Here are the 2 most common situations.
Skewed quota information
Occasionally quota data becomes skewed and requires a recheck. PM Software Stack includes automated script which does more than just rechecks the quota. This includes user names not shown, wrong used amounts etc.
Situations where this maybe necessary are and may fix:
- Quotas show up as 0 (limits or used)
- Removed accounts still showing up on repquota
- Reported usage does not reflect reality (ie. shows more used for a user than actually is used)
- Accounts missing from report
cd /scripts/util quotaoff -av ./quotaFix.php
After a while quota has been checked and new quota files have been created, and quota will be re-enabled automatically.
If you get write permission error, see next section.
Permission denied aquota.user for root
So something went awry within kernel and even root does not have permission to these files?
Reboot server, then after rebooting login and issue following commands:
rm -rf /home/aquota*.new cd /scripts/util ./quotaFix.php
This ought to be fixed now.