![]() By doing this you use up a lot of disk space unnecessarily. Many people do this because they think that it will be useful in the long run but we all know that they tend to be useless when a server failure occurs. To delete all fantastico backups use the following command: rm -rfv /home/*/fantastico_backups 2) Move your backup files to a backup serverĪnother main reason is storing the backup files of your hosting server on the server itself. You can delete all user’s cPanel backups by using the following command: for user in `/bin/ls -A /var/cpanel/users` do rm -fv /home/$user/backup-*$ done If you have the backup feature in the cpanel enabled this will definitely be the case. One of the main reasons for a large amount of the server’s disk space running out is when user’s start making backups in the server itself instead of removing them after a download. 1) Delete user cPanel and Fantastico backups The only way that you can increase the potential and efficiency of your server is to free up your disk space.įollow the steps and your server will be more efficient than ever. You start running out of disk space due to your server filling up due to the increase in customers. So everything in the link is technically correct, but easily misleading in my opinion and not applicable to the original question of recovering VMDK space using the Host system.Getting customers is beneficial for any business but behind the scenes, we know that it causes some issues. It has to be run from the Linux (not Windows) client, not the host. Īgain this is a Linux command that if run from the HOST sytem will have zero effect on a client VMDK. This for example creates a 100MB size file filled with zero's If your machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition. Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:Ĭat /dev/zero > /home/zero.fill sync sleep 1 sync rm -f /home/zero.fill Note that you have multiple partitions that you have to repeat the above command to zero out for each partition. To fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.Īs this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". As written it's technically correct, but it implies that it's effecting a VMDK from the host but it does not.Ĭat /dev/zero > zero.fill sync sleep 1 sync rm -f zero.fill If it's run within a Linux client VM it will incidentally act on that Linux (not Windows) VM as would any other linux command, but run from the HOST system, it has no effect on a client VM. This is a Linux command to cleanup Linux repositories, it's completely unrelated to VMs. ![]() To clear out the local repository of retrieved package files. ![]() Wila, your referenced link while informative is also in my opinion inadvertently misleading, here's why I say that:īefore we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space.įor example, on Debian-based VMs, you can run
0 Comments
Leave a Reply. |