I'm a newbie to KVM, but have been running Proxmox for a few months without any problems - in fact the more I realise how awesome Proxmox is, the more I'm in awe of the developers!
However, I've just had what appeared to me to be some kind of hardware failure on the host. My VMs were reporting i/o errors and mounting their drives read-only and things. I couldn't create a new VM either.
After drawing up elaborate rescue plans while my phone rang constantly, I suddenly realised that a df -h on the host showed I was 100% on /dev/mapper/pve-data and almost full on /dev/mapper/pve-root
So now I've removed some disk files and all is OK.
I would have been nice to have had some obvious warning in the GUI - maybe just a red color on the local storage icon or something like a message?
PS: I thought KVM .raw disk files would only use up the physical space they were using in the virtual space (that is, thin provisioning)? But I see though that if I create a disk that's 100G, it creates a 100G .raw file, even though the VM's only using 20G. Is that right?
However, I've just had what appeared to me to be some kind of hardware failure on the host. My VMs were reporting i/o errors and mounting their drives read-only and things. I couldn't create a new VM either.
After drawing up elaborate rescue plans while my phone rang constantly, I suddenly realised that a df -h on the host showed I was 100% on /dev/mapper/pve-data and almost full on /dev/mapper/pve-root
So now I've removed some disk files and all is OK.
I would have been nice to have had some obvious warning in the GUI - maybe just a red color on the local storage icon or something like a message?
PS: I thought KVM .raw disk files would only use up the physical space they were using in the virtual space (that is, thin provisioning)? But I see though that if I create a disk that's 100G, it creates a 100G .raw file, even though the VM's only using 20G. Is that right?