Suggestion: WHM should run a cron job, daily or weekly, to /scripts/fixquotas

spaceman

Well-Known Member
Mar 25, 2002
565
16
318
If you do a search in these forums, you'll see lots of advice being given to run /scripts/fixquotas to fix up the reporting of disk usage of hosting accounts.

Which tells us that, for whatever reasons, sometimes disk usage report for hosting account in WHM gets out of sync.

Why not include in WHM a cron job that runs /scripts/fixquotas on a regular basis, as standard?

I just manual ran /scripts/fixquotas on a single tenant server with just two accounts, and the reported disk usage changed like this:


account 1: 546 Mb > 91191 Mb
account 2: 243 Mb > 112134 Mb

Wow!!! No wonder a full cPanel backup was taking ages!!!
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
17,470
2,843
363
cPanel Access Level
Root Administrator
Hey hey! The reason we don't do that is due to the CPU usage it can cause. In your example, I bet the "account 2" took quite a while to run.

In general, I wouldn't expect the files to get out of sync or else there would be daily threads about this happening with many users - it just seems to be an occasional issue, probably after a migration or major change on the server.
 

spaceman

Well-Known Member
Mar 25, 2002
565
16
318
Fair enough, but I would like the *option* to configure this to run using the WHM dashboard. Any performance hit would be on me.

But I know I can setup up my own cron to do the same if I want.

Thx again.
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
17,470
2,843
363
cPanel Access Level
Root Administrator
You have to think about the flip side, though. You are reasonable enough to say something like the "performance hit would be on me" but we'd instantly get "I checked this box and now the server is slower, why would you make that an option" type of messages :D
 

spaceman

Well-Known Member
Mar 25, 2002
565
16
318
I get your point, but, there are of course no end of bad/clumsy/accidental things one could do with WHM acccess, right now.

Me, I'd include it in WHM, with a prominent warning/advisory alongside it, e.g. "CAUTION: running this script may cause performance issues for your site. Use at your own risk".

You'd think a disclaimer like that would be sufficient to satisfy everyone.