Broken Filesystems form VMs on ProxMox 2.x and local disks

May 16, 2013
25
0
21
hi,

I migrate from ProxMox 2.x with several (KVM) VMs to a cluster enabled ProxMox 3.1. I do that with shutdow the VM, copy the image to the new host, convert it to raw and dd it to the lvm ... I thought, that there must be a problem with the converting, but I started the original VM on the old ProxMox again ... and broken filesystem ...


I have now a second VM which has also a complete damaged filesystem (all ext4). The images are standard qcow2 files on a local Raid1 (Megaraid with battery) and all have standard options. Inside a VM I have Debian Squeeze with LVM and ext4 filesystems.

I absolutely don't have any idea, why this happens. The VMs runs ~100 days. :-( I have at least three other VMS which I don't touch the next days and keep backup up to date ... but I think, that these VMs have also broken filesystems.

cu denny

ps. I have subscriptions for all hosts.