• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Disk quota exceeded - but its not

Amin Taheri

Golden Pleskian
Plesk Certified Professional
Domain has overuse allowed, and has 10gb limit set on resource limits, and is only using 1gb in the entire domain directory, including log files, etc.

When going into the domain in Plesk CP and into file manager, I try and create a folder and it gives an error.

Error: Unable to create directory /httpdocs/test1: filemng failed: mkdir: cannot create directory `/var/www/vhosts/domain.com/httpdocs/test1': Disk quota exceeded
filemng: Error occured during /bin/mkdir command.

Besides the error message misspelling occurred, it is also happening in error as the domain has plenty of space available to it (over 9 gb) and overuse is allowed both on the domain level an on the client level. On both client and domain the user has gigs of space to spare.

I have also tried to recalculate by running
/usr/local/psa/admin/sbin/statistics --calculate-one --domain-name=domain.com

And that made no change.

What is the problem here?
 
mkdir: cannot create directory `/var/www/vhosts/domain.com/httpdocs/test1': Disk quota exceeded
filemng: Error occured during /bin/mkdir command.

It may be related to lack of free inodes but not lack of free disk space. Check it with 'df -i' command.
 
Thanks, but unfortuantely thats not it - the file system is only at 4% used for IUse%

Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sdb1 25M 968K 25M 4% /var/www/vhosts
 
I found how to solve this problem, it's really easy, but it was really hard to find what's the problem :)

chown -R "username to the plesk":psaserv httpdocs/
 
Hi Norbert,

I have the same problem - one of my clients is using 1.8GB of disk space, but Plesk says he's using nearly 7GB... Can't be right. Even with database usage he's not even using 2GB in total.

How did you solve the problem then? All files in my client's httpdocs directory belong to to him, and du -sh shows me the total of 1.8GB?
 
Hello Jay!

When I had this problem, it was caused by the bad chown ( another plesk user had the right, to write in the folder (I don't know, how could this happened), when I changed the chown, my client could create a new folder). If I were you, I'd make a copy of your client files and database after that I'd delete your client's account and recreate it and copy everything back.

If your problem didn't solve and you need another advice, don't hesitate to contact me by PM or email!

Best Regards!

Norbert Csupka
 
Hi Norbert,

thanks for letting me know - so basically if files in my clients account belong to another user, they count as that other user's quota, correct?

In which case I have a different problem, but I was wondering how Plesk works out the quota for a client. Here's a screenshot of my statistics for the client in question - he's physically got 1.9GB in his /var/www/vhosts/hisdomain.com directory. Statistics says he uses a LOT of space for "other" stuff...

Can you shed some light on this?
 

Attachments

  • Screen-Shot-2012-01-03-at-21.19.22.png
    Screen-Shot-2012-01-03-at-21.19.22.png
    28.5 KB · Views: 17
I would have to agree - conventional wisdom would lead me to believe that if another user owned files and it didnt count those files towards this users quota, then plesk would under report his usage insted of grosly over report right?
 
Must still say that there is not yet an answer to this question, it is still an open bug. Just one of about 100 bugs in Plesk that go unanswered and unfixed over the years.
 
Back
Top