have you looked at storage over-provisioning settings ??
On Thu, Oct 3, 2013 at 11:53 AM, Indra Pramana <in...@sg.or.id> wrote: > Dear all, > > We face a major problem after upgrading to 4.2.0. Mounting from KVM hosts > to secondary storage seems to fail, every time a new VM instance is > created, it will use up the / (root) partition of the KVM hosts instead. > > Here is the df result: > > ==== > root@hv-kvm-02:/home/indra# df > Filesystem 1K-blocks Used > Available Use% Mounted on > /dev/sda1 4195924 > 4195924 0 100% / > udev 132053356 4 > 132053352 1% /dev > tmpfs 52825052 440 > 52824612 1% /run > none 5120 > 0 5120 0% /run/lock > none 132062620 0 > 132062620 0% /run/shm > cgroup 132062620 0 > 132062620 0% /sys/fs/cgroup > /dev/sda6 10650544 2500424 > 7609092 25% /home > 10.237.11.31:/mnt/vol1/sec-storage2/template/tmpl/2/288 4195924 > 4195924 0 100% /mnt/5230667e-9c58-3ff6-983c-5fc2a72df669 > ==== > > The strange thing is that df shows that it seems to be mounted, but it's > actually not mounted. If you noticed, the total capacity of the mount point > is exactly the same as the capacity of the / (root) partition. By right it > should show 7 TB instead of just 4 GB. > > This caused VM creation to be error due to out of disk space. This also > affect the KVM operations since the / (root) partition becomes full, and we > can only release the space after we reboot the KVM host. > > Anyone experience this problem before? We are at loss on how to resolve the > problem. > > Looking forward to your reply, thank you. > > Cheers. >
