One of our servers (Debian 6.0.10 Squeeze) scheduled virtualmin backups fail if the user is close to the quota limit: 878.64 MB of 1000 MB (87%).
The MySQL backup reports:
Creating backup for virtual server example.com ..
[...]
Dumping MySQL database example_database ..
.. dump failed! mysqldump: Got errno 122 on write
[...]
“Got errno 122 on write” is a typical error for disk space or quota issues. So, I assume, this is a side effect of the latest virtualmin update, which now runs backups as the user (not root any more) and therefore consumes disk space and the user’s quota while creating the backup.
The interesting thing on this server is, that it has one partition only:
Not an ideal solution, because I can not predict if other users will run into the same problem of course and setting the quota (here: 1000 MB) kind of hard-coded is a woefully solution, too.
Weird… package “webmin-virtual-server” version 4.13.gpl-2 is currently installed on this machine.
I will monitor the backups over the next days and report back next week.
The problem still exists. Package webmin-virtual-server-4.13.gpl-2 is installed and the user consumes approx. 90% of his server quota. The backups fail when writing the MySQL backup:
Dumping MySQL database example_database ..
.. dump failed! mysqldump: Got errno 122 on write
I also got a virtuamin warning via email (“Disk quota exceeded”) at the same time:
Disk usage for group exmaple on filesystem / has reached 100% of the
allowed quota.
1000.42 MB of disk space is being used, out of a maximum of 1000 MB.
I appreciate any suggestions (I re-instituted my workaround mentioned above).