Backup file big

M

mechanicus

Renowned Member
Mar 30, 2009
54
0
71
Germany
Hello,

one of my vm's (Fedora 14) has an unexpected big backupfile of 75 GB.
The raw-image is 80 GB and I get in the running machine the following output:
Code: 
$ df -h
Dateisystem           Size  Used Avail Use% Eingehängt auf
/dev/vda1              78G   35G   40G  47% /
tmpfs                1007M  364K 1007M   1% /dev/shm

The backup file of another machine with Fedora 12 is 48 GB, the raw image 100 GB and 37 GB in use.
That's as expected.

Is there any thing wrong?

Code: 
# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-50
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-6-pve: 2.6.32-50
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6
 
Last edited:
use compression.
 
dietmar said:
create a big file containing zeros, then delete that file.
Click to expand...
Oh, of course, thank you!

My steps:
1.) Booting the vm by a rescue cd, without automatic mounting the image (/dev/vda1).
2.) Mounting the image (dev/vda1) manualy to /mnt in the rescue system.
3.) # cat /dev/zero > trash (the file is created and is now filled with zeros)
4.) Abord the process by typing <ctrl-c>, if the cpu load of the vm is 0%
5.) # rm /mnt/trash (the file trash was 43GB here)
6.) # umount /dev/vda1
7.) # fsck.ext4 -v -f -c /dev/vda1 (for security reasons)
8.) # poweroff

My new backup fil is 35GB, previously it was 78GB (raw image is 80GB) :)
 
You must log in or register to reply here.
Top Bottom