Submitted by jfquestiaux on Thu, 10/06/2011 - 08:18
Hi,
On one of my virtual servers, I can't install scripts because of the following message :
Failed to extract source : Failed to create target directory : mkdir: cannot create directory `/home/xxx/public_html/squirrelmail': Disk quota exceeded
Of all the virtual servers on this machine, it is the only one where I changed the quota from the default 2Go to 3Go from which 1.97 Go are used. But it used to work fine.
Yesterday, there has been a major problem with the hosting company (Gandi), something related to a filer system and since then, I am experiencing this problem.
Probably something in the calculation of the disk space is askew but I don't know how to fix it. Any idea ?
Best regards.
Status:
Closed (fixed)
Comments
Submitted by andreychek on Thu, 10/06/2011 - 09:38 Comment #1
Howdy -- the error you're seeing is actually one that's returned by the filesystem... so the underlying system really does think your user is over quota.
Can you log into your server, and run these two commands:
quota -v USERNAME
quota -g USERNAME
That should show off some quota details, and help give us an idea as to where the problem lies.
Submitted by jfquestiaux on Thu, 10/06/2011 - 09:57 Comment #2
Hello Andrey,
Here are the outputs :
quota -v adminlunjf Disk quotas for user adminlunjf (uid 1016): Filesystem blocks quota limit grace files quota limit grace /dev/root 3142096 3145728 3145728 10230 0 0
quota -g adminlunjf quota: group adminlunjf does not exist.
Submitted by andreychek on Thu, 10/06/2011 - 10:22 Comment #3
Okay, so it does look like that user has passed their 3GB quota.
If you go into Edit Virtual Server for that domain, and click Quotas and Limits, what details do you see after the line beginning with "Home disk space used (including sub-servers)"?
Submitted by jfquestiaux on Thu, 10/06/2011 - 11:06 Comment #4
OK. my mistake. There was a file that was eating up the space and I did not notice!
Sorry to have bothered you with that. Everything install fine now.
Thanks again.
Submitted by JamieCameron on Thu, 10/06/2011 - 11:28 Comment #5
Great, glad you got it fixed..
Submitted by Issues on Thu, 10/20/2011 - 11:46 Comment #6
Automatically closed -- issue fixed for 2 weeks with no activity.