Hi, The low disk space is controlled by a parameter in the engine called FreeSpaceCriticalLowInGB, and can be configured using the cli tool engine-config. you should be able to set it to something like 4 GB or maybe 3GB so you can start your vms with the following command: engine-config -s FreeSpaceCriticalLowInGB=3 After doing this you have to restart the engine service (service ovirt-engine restart) for the changes to take effect. If you want to see what the current value is use engine-config -g FreeSpaceCriticalLowInGB. To see a list of all configurable values you can use engine-config --list Thanks, Gadi Ickowicz ----- Original Message ----- From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "users" <users@ovirt.org> Sent: Tuesday, January 7, 2014 4:57:18 PM Subject: [Users] how to temporarily solve low disk space problem preventing start of VM Hello, test cluster with two nodes and GlusterFS DC on f19 and 3.3.2, using gluster version 3.4.2 from f19 updates-testing repo. Unfortunately I have only small local disk quite occupied by existing VMs. About 4Gb free. I had VMs started and then I shutdown them. Trying to power on any VM I get: Error while executing action: c6s: Cannot run VM. Low disk space on target Storage Domain gvdata. On SPM node (node02) that is the only one active I have: /dev/mapper/fedora-DATA_GLUSTER 30G 23G 7.8G 75% /gluster/DATA_GLUSTER node01.mydomain:gvdata 30G 26G 4.6G 85% /rhev/data-center/mnt/glusterSD/node01.mydomain:gvdata Can I tweak this low disk warning in any way? How does engine make this kind of check? Thanks in advance Gianluca _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users