<div dir="ltr"><div><div><div>Hi Cesar,<br><br></div>Out of sync with cache=directsync happen in very specific cases. Here is the decription of  one of them: <a href="http://forum.proxmox.com/threads/18259-KVM-on-top-of-DRBD-and-out-of-sync-long-term-investigation-results?p=108099#post108099">http://forum.proxmox.com/threads/18259-KVM-on-top-of-DRBD-and-out-of-sync-long-term-investigation-results?p=108099#post108099</a><br><br></div>Best regards,<br></div>Stanislav<br><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 13, 2015 at 7:02 PM, Cesar Peschiera <span dir="ltr"><<a href="mailto:brain@click.com.py" target="_blank">brain@click.com.py</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi to all<br>
<br>
I use directsync in my VMs with DRBD 8.4.5 in four nodes (LVM on top of DRBD), since some months ago, never did have problems (all sunday days, a automated system verify all storages DRBD),<br>
<br>
These are the version of packages of my PVE nodes:<br>
<br>
In a pair of nodes:<br>
Shell# pveversion -v<br>
proxmox-ve-2.6.32: 3.3-139 (running kernel: 3.10.0-5-pve)<br>
pve-manager: 3.3-5 (running version: 3.3-5/bfebec03)<br>
pve-kernel-2.6.32-27-pve: 2.6.32-121<br>
pve-kernel-3.10.0-5-pve: 3.10.0-19<br>
pve-kernel-2.6.32-28-pve: 2.6.32-124<br>
pve-kernel-2.6.32-29-pve: 2.6.32-126<br>
pve-kernel-2.6.32-34-pve: 2.6.32-139<br>
lvm2: 2.02.98-pve4<br>
clvm: 2.02.98-pve4<br>
corosync-pve: 1.4.7-1<br>
openais-pve: 1.1.4-3<br>
libqb0: 0.11.1-2<br>
redhat-cluster-pve: 3.2.0-2<br>
resource-agents-pve: 3.9.2-4<br>
fence-agents-pve: 4.0.10-1<br>
pve-cluster: 3.0-15<br>
qemu-server: 3.3-3<br>
pve-firmware: 1.1-3<br>
libpve-common-perl: 3.0-19<br>
libpve-access-control: 3.0-15<br>
libpve-storage-perl: 3.0-25<br>
pve-libspice-server1: 0.12.4-3<br>
vncterm: 1.1-8<br>
vzctl: 4.0-1pve6<br>
vzprocps: 2.0.11-2<br>
vzquota: 3.1-2<br>
pve-qemu-kvm: 2.1-10<br>
ksm-control-daemon: 1.1-1<br>
glusterfs-client: 3.5.2-1<br>
<br>
In other pair of nodes:<br>
Shell# pveversion -v<br>
proxmox-ve-2.6.32: 3.3-139 (running kernel: 3.10.0-5-pve)<br>
pve-manager: 3.3-5 (running version: 3.3-5/bfebec03)<br>
pve-kernel-3.10.0-5-pve: 3.10.0-19<br>
pve-kernel-2.6.32-34-pve: 2.6.32-139<br>
lvm2: 2.02.98-pve4<br>
clvm: 2.02.98-pve4<br>
corosync-pve: 1.4.7-1<br>
openais-pve: 1.1.4-3<br>
libqb0: 0.11.1-2<br>
redhat-cluster-pve: 3.2.0-2<br>
resource-agents-pve: 3.9.2-4<br>
fence-agents-pve: 4.0.10-1<br>
pve-cluster: 3.0-15<br>
qemu-server: 3.3-5 <-particularly made by Alexandre<br>
pve-firmware: 1.1-3<br>
libpve-common-perl: 3.0-19<br>
libpve-access-control: 3.0-15<br>
libpve-storage-perl: 3.0-25<br>
pve-libspice-server1: 0.12.4-3<br>
vncterm: 1.1-8<br>
vzctl: 4.0-1pve6<br>
vzprocps: 2.0.11-2<br>
vzquota: 3.1-2<br>
pve-qemu-kvm: 2.2-2 <-particularly made by Alexandre<br>
ksm-control-daemon: 1.1-1<br>
glusterfs-client: 3.5.2-1<br>
<br>
</blockquote></div></div></div>