Search results

Same problem here with Dell 740xd. I'll try the 6.0....

It works !!!!! ;);)

Strange thing ...me too in another "old" cluster 3.1 (same design 2 node drbd in active-active) never had any issue and the virtual machine have all the vm disks in writethrough mode since the beginning This is the pveversion: proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)...

Yes in this cluster I have HW RAID + DRBD and the cache was in writethrough but there are 11 VM in this two-node cluster, all in writethrough, the one "problematic" is a heavy loaded varnish cache... now I set it in directsync and since then I haven't any error..... P.S No another error...

Hi thanks for posting.. How can you say that is a read error?? Your VM affected did survive with this error?? And ... if we have Windows VM guests :( no btrfs at all!! Damn we have a LOT of VM in drbd........... gianni.bet

Hi we have the same exactly problem The change to directsync did solve the issue??? Our versions: root@kvmg1-ver3:~# pveversion -v proxmox-ve-2.6.32: 3.3-147 (running kernel: 2.6.32-37-pve) pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e) pve-kernel-2.6.32-37-pve: 2.6.32-147 lvm2...