From: Jamie C. <jca...@we...> - 2010-08-30 22:08:23
|
On 30/Aug/2010 08:09 MAR <we...@ro...> wrote .. > Jamie Cameron <jca...@we...> wrote .. > > On 29/Aug/2010 21:07 MAR <we...@ro...> wrote .. > > > I am restoring a backup (actually moving a site from one server to another), > > but > > > continually get errors about a lack of disk space on some of the sites I am > moving. > > > > > > I think I traced this to be an issue with large mail files (or large amount > of > > > space used in a given users directory). So, I changed the default 50mb per > user > > > on the new server to 200mb to make sure it could accommodate that space. I > still > > > get errors that the disk quota was exceeded. > > > > > > This situation only exists for sites where the user has a lot of mail. Here > > is > > > a sample of the error it spits out (with the domain name changed): > > > > > > /bin/tar: ./.backup/thisdomain.com_mail_files: Wrote only 7168 of 10240 bytes > > > /bin/tar: ./.backup/thisdomain.com_mysql_thisdomain.gz: Cannot write: Disk > quota > > > exceeded > > > /bin/tar: Skipping to next header > > > /bin/tar: ./.backup/thisdomain.com_virtualmin_bw: Cannot write: Disk quota > exceeded > > > /bin/tar: Skipping to next header > > > /bin/tar: ./.backup/thisdomain.com_web: Cannot write: Disk quota exceeded > > > /bin/tar: ./.backup/thisdomain.com_webalizer_conf: Cannot write: Disk quota > exceeded > > > /bin/tar: Skipping to next header > > > /bin/tar: Archive contains obsolescent base-64 headers > > > /bin/tar: Error exit delayed from previous errors > > > > > > > > > Any ideas to fix or is this a bug that is going to, hopefully, be fixed at > some > > > point? > > > > This could be caused by some files existing on the destination system already > > owned by the user or group of the domain being restored. You could check with > commands > > like : > > > > find / -user domain > > find / -group domain > > > > where domain is the admin username of the domain being restored. > > > > Normally the Virtualmin restore process will set quotas to be the same as > > on the original system, so unless the domain was over quota originally there > > should be enough space to restore all of its files. > > Actually, no, that doesn't do anything to fix the issue. The existing system has > no users/groups or anything related to the ones being put in. Definitely seems > tied to users with a lot of mail....though maybe that isn't the issue. Do you happen to know how close this domain was to its quota on the original system when the backup was taken? I just thought of a failure mode that could happen if a domain was close to quota, and stores mailboxes outside of the home directory (like in /var/mail). One work-around is to disable quotas, do the restore, then re-enable quotas. This can be done at System Settings -> Virtualmin Configuration, by changing "Quota setup for domain and mail users?" to "No". - Jamie |