Search results

Thanks for looking into this dietmar :-) We've now written a simple perl script that checks for inconsistency so we can manually fix it, and we eagarly await pve v2.0!

I've just created an ISCSI connection (based on FreeNAS, and following http://pve.proxmox.com/wiki/Storage_Model#LVM_Groups_with_Network_Backing) - and it still does it (using the method I outlined in my first post). No DRBD anywhere in sight! Let me know if there's anything else you'd like me...

Did anyone manage to replicate this issue? Thanks

Yes, it does. I've just switched both of my testing nodes o 2.6.32-4-pve and re-done the test (from my first post). Still happens in just the same way. The only way I've found to fix it is reboot the host, or use the 'dmsetup remove' line from my first post.

Correct. Once I delete the VM, 'lvscan' on both machines shows that the LV has gone (it's not in the list). On the primary node, /proc/partitions no longer has the 'dm-' entry that was for that LV. On the secondary node, the dm- entry is still in /proc/partitions.

I've tested, and this doesn't solve it: and the problem still shows (the entry is still in /proc/partitions). Just tested this too, with the same method as above - no change, the problem still shows up in the same way.

Hi all I'm running a Proxmox 1.8 cluster with DRBD, as described here: http://pve.proxmox.com/wiki/DRBD (Versions below) I think I've found a problem with deleting virtual machines and volumes. I've been able to replicate it on a test cluster, so it's not just my system! My master proxmox host...