These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Restore Backup fails with disk quota exceeded but quota limit not enabled on the new forum.
When restoring a virtualmin created backup to a new server the restore process fails once it reaches 1gb with a "disk quota exceeded" message when extracting the TAR of the home directory.
I've tried this a few times now and checked that disk quotas in virtualmin for the virtual server are not enabled on either the old server or the new server.
I must be missing something... Is there a setting to override the enforced 1gb limit when running a restore?
Hrm, that seems unusual.
It sounds like there could be a quota setup that Virtualmin isn't seeing for some reason...
If you log into your server as root, and type this command, what output do you receive:
quota -v USERNAME
Also, another option for making sure Virtualmin is correctly sync'd with your system quotas is to go into Limits and Validation -> Check Disk Quotas, and click "Check Now".
-Eric
Thanks for your response Eric. Have been looking into this further today but am still at loss.
After inputting quota -v USERNAME i get:
On the old server...
Disk quotas for user xxxxx (uid 1007): none
On the new server (after deleting the old backup and restoring from a newly created backup)....
Filesystem blocks quota limit grace files quota limit grace /dev/simfs 1060104* 1048576 0 none 2265 0 0
The places i've checked include...
virtualmin->system settings->account plans ->default plan
virtualmin->system settings->server templates
webmin->system->disk quotas
A couple of these had (what appear to be set by default) 1gb limits initally but have removed these and am still having troubles.
On the new server after each restore i have been deleting the newly created Virtual Server before attempting a new restore.
This is a bit of a problem as it applies to all of the Virtual Servers over 1gb I have.
After a failed restore I can remove the quota limit from the failed restore of the Virtual Server and then copy the files manually from the backup tar.gz to the home directory. This is somewhat impractical do to for each Virtual Server over 1gb and perhaps more importantly looking forward it would be nice to have confidence in being able to take backups and know that they can be restored easily.
Would you be able to take a guess as to whether this is an issue with a limit imposed during the backup or a limit imposed during the restore?
Plus is there anywhere else I show be looking or is there possibly a way to turn disk quotas off?
Howdy,
If you go into Webmin -> System -> Disk Quotas, what does it say under "Action"? It would likely be either "Enable Quotas" or "Disable Quotas". If quotas are enabled, you could disable them there.
-Eric
ah knew there must be a way to turn quotas off, i'd missed that.
unfortunately it just gives....
quotaoff: quotactl on /dev/simfs [/]: Invalid argument
Hrm, so are you by chance using an OpenVZ-based VPS? We seem to run into some of the strangest problems with those :-)
What output do you see if you run the command "mount"?
-Eric
Interestingly have also just noticed that i don't have a Virtualmin->Limits and Validation->Check Disk Quotas menu entry on the old server. Only on the new one.
Running mount i get...
/dev/simfs on / type reiserfs (rw,usrquota,grpquota)
Btw. My Virtualmin installtion is basically new. Can't really think of anything i did beyond installing it onto a fresh image of Ubuntu 10.04. Got the my 1gb problem with restoring backups straight away after that.
My Virtualmin installtion is basically new. Can't really think of anything i did beyond installing it onto a fresh image of Ubuntu 10.04.
Well, the issue is that some VPS's don't play nicely with quotas. I suspect you'd end up with the same problem on another distro.
Here's another thing which may get it to stop trying to set your quotas --
If you go into System Settings -> Virtualmin Configuration, set "Quota setup for domain and mail users" to "No".
After that, does your restore work properly?
-Eric
If you go into System Settings -> Virtualmin Configuration, set "Quota setup for domain and mail users" to "No".
Already tried setting this to no and tried restoring,
Well, the issue is that some VPS's don't play nicely with quotas. I suspect you'd end up with the same problem on another distro.
I've used virtualmin on other OpenVz servers before and it's played fine then.
Just thought i'd and see if anyone had any ideas as it seemed at the time like a fairly cut and dry type issue.
Really appreciate your help with everything especially given the difficultly of trying to provide suggestions when your not directly in front of the problem. As much thought i'd post here just incase it was a known issue of some sort.
Will keep looking into the problem and if/when i find a soluton will post back here.
Well, it does indeed work on some OpenVZ setups. It seems to be hit or miss.
The only time we really seem to run into this problem is on OpenVZ though -- if you search for "reiserfs quotas" in the forums here (the filesystem you're using is reiserfs), you'll see a big long string of people who've really struggled to get this to work, all of which are on OpenVZ.
Quotas on other VPS types seem to work without any hassle.
I'll offer though that even if quotas aren't going to work, it should be possible to get Virtualmin to stop trying to use them.
So you're saying that once you've gone into all those various areas, and disabled quotas -- that you're still receiving that message when doing a restore about running out of quota space? If that's the case, I may give Jamie a shout and see if he has any thoughts on how to get around that.
-Eric
I am running VirtualMin on a dedicated CentOS server. I want to restore my backup on a separate server (same hardware and OS).
If the backup file is larger than 1 GB I'm getting the "Restore Failed" error. The restore of backup files with less than 1 GB is fine.
I tried all the hints mentioned above without success.
Any ideas?
Andreas
Howdy,
Is your /tmp directory on it's own partition? If so, how large is that partition? One explanation for what you're seeing is that /tmp might be running out of space as the backup file is unpacked.
-Eric
/tmp is under / and has no limitations (except disc space).
But I found a workaround for (my) problem.
Basicly I restored direct from the ftp-server where the backup was stored. That was the situation when I got the error.
Now I copied via ftp the backup file to the second (new) server. From the local file I was able to restore.
Afterwards I tried to backup directly to the second (new) server via ftp with the "one file option". This 10 GB file was also restoreable.
For me this "workaround" is probably better than anything else.
Andreas
Just wanted to post an update on my original problem.
I ended up becoming ridiculously busy and had to put my migration plans on hold (plus i can't recall receiving any email notification as to your post on 2011-04-02 and only became aware of it after Technopaintings posts) - so sorry if it seems i didn't reply.
I just attempted a fresh backup and restore (identical to those i was making a month back) and low and behold the restore worked flawlessly.
I have absolutely no explanation as to why this now suddenly works (could of been a package update or a change to the virtualization management perhaps) but i'm happy to report i'm no longer experiencing this behaviour.
Many thanks for your help Eric.
I had this same problem "disk quota exceeded" when trying to migrate a 10GB backup from a CPanel server.
As a workaround, I tried to open up the backup file, untar the home directory archive and remove some of the files in public_html. I figured I could copy them over manually afterwards. But when I ran the tar -xf command on the home directory archive, I got the "disk quota exceeded" errors. So the errors had nothing to do with Virtualmin, they were being produced by tar. However unlike Virtualmin's migrate script, the tar command didn't clean up after itself. So when I did "df -i", I could see that all my inodes were used up.
I added some more inodes to my VPS and the restore worked fine.
There needs to be a way to bypass or exclude the quota feature during a restore. I tried everything, setting it on the new server, the templates etc etc. The ONLY way I got it to work was to go to the old server, enable quotas, set the quota, make another backup, and then restore it on the new server. I even tried setting the quota as soon as it hit that restore point but it still blew up. why doesnt virtualmin-restore have a --exclude-feature quota ?????