Hi all,
I have an instance of proxmox running on a local disk with 4TB in a RAID 10.
I have a virtual windows server (2012r2) with a disk of 2TB
The Virtual Image is located in /var/lib/vz/images/101/vm-101-disk-1.qcow2
In the past I've done snapshots before major updates to roll back in case of an issue. After a few weeks to months I delete the snapshots.
I did that just this past weekend and while the snapshots are now gone from being seen in the webgui under the VMID's snapshot list and from the configuration file as well in /etc/pve/qemu-server/101.conf, the actual data thats being used on the disk is showing to be about 3.5TB which is way more than the 2TB that was allocated to the virtual disk in the first place.
The config file looks like:
bootdisk: virtio0
cores: 12
ide2: none,media=cdrom
memory: 10240
name: kerio.server.local-192.168.30.71
net0: virtio=82:F7:C2:16:A4:98,bridge=vmbr0
numa: 0
onboot: 1
ostype: win8
smbios1: uuid=9f834733-17d1-4a8b-b3c6-0a5d7101eefd
sockets: 1
virtio0: local:101/vm-101-disk-1.qcow2,format=qcow2,size=2000G
This is running on a proxmox 3.4-11 instance, not yet upgrade to the latest verion.
The Windows server itself is also showing me 1.43TB free of a 1.95TB disk so I know its using well less than the 2TB of data that was allocated to the virtual server on the physical disk.
A df shows:
Filesystem Size Used Avail Use% Mounted on
udev 10M 0 10M 0% /dev
tmpfs 1.6G 336K 1.6G 1% /run
/dev/mapper/pve-root 95G 1.6G 89G 2% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.2G 31M 3.1G 1% /run/shm
/dev/mapper/pve-data 3.5T 3.5T 11G 100% /var/lib/vz
/dev/sda2 127M 142K 126M 1% /boot/efi
/dev/fuse 30M 16K 30M 1% /etc/pve
However a du -sh vm-101-disk-1.qcow2 is showing me 3.5TB being used
I'd like to know how to flush out the crude inside the qcow2 file to reclaim the space on the server and have virtual disk showing as the proper disk size again.
Thanks for the help
I have an instance of proxmox running on a local disk with 4TB in a RAID 10.
I have a virtual windows server (2012r2) with a disk of 2TB
The Virtual Image is located in /var/lib/vz/images/101/vm-101-disk-1.qcow2
In the past I've done snapshots before major updates to roll back in case of an issue. After a few weeks to months I delete the snapshots.
I did that just this past weekend and while the snapshots are now gone from being seen in the webgui under the VMID's snapshot list and from the configuration file as well in /etc/pve/qemu-server/101.conf, the actual data thats being used on the disk is showing to be about 3.5TB which is way more than the 2TB that was allocated to the virtual disk in the first place.
The config file looks like:
bootdisk: virtio0
cores: 12
ide2: none,media=cdrom
memory: 10240
name: kerio.server.local-192.168.30.71
net0: virtio=82:F7:C2:16:A4:98,bridge=vmbr0
numa: 0
onboot: 1
ostype: win8
smbios1: uuid=9f834733-17d1-4a8b-b3c6-0a5d7101eefd
sockets: 1
virtio0: local:101/vm-101-disk-1.qcow2,format=qcow2,size=2000G
This is running on a proxmox 3.4-11 instance, not yet upgrade to the latest verion.
The Windows server itself is also showing me 1.43TB free of a 1.95TB disk so I know its using well less than the 2TB of data that was allocated to the virtual server on the physical disk.
A df shows:
Filesystem Size Used Avail Use% Mounted on
udev 10M 0 10M 0% /dev
tmpfs 1.6G 336K 1.6G 1% /run
/dev/mapper/pve-root 95G 1.6G 89G 2% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.2G 31M 3.1G 1% /run/shm
/dev/mapper/pve-data 3.5T 3.5T 11G 100% /var/lib/vz
/dev/sda2 127M 142K 126M 1% /boot/efi
/dev/fuse 30M 16K 30M 1% /etc/pve
However a du -sh vm-101-disk-1.qcow2 is showing me 3.5TB being used
I'd like to know how to flush out the crude inside the qcow2 file to reclaim the space on the server and have virtual disk showing as the proper disk size again.
Thanks for the help
