Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi
I use DRBD Proxmox VE 8.3 with 2.2 and a configuration Primary / Secondary on network computers trajeta Gigabyte
Basically I use it to keep a copy of the LV of the primary machine.
When I run, /sbin/drbdadm verify all I find that there are many messages like this::
Dec 31 09:18:04 pro01 kernel: block drbd2: Out of sync: start=147170512, size=248 (sectors)
Dec 31 09:18:04 pro01 kernel: block drbd2: Out of sync: start=147195176, size=2504 (sectors)
Dec 31 09:18:05 pro01 kernel: block drbd2: Out of sync: start=147218992, size=11472 (sectors)
Dec 31 09:18:05 pro01 kernel: block drbd2: Out of sync: start=147230472, size=104 (sectors)
Dec 31 09:18:05 pro01 kernel: block drbd2: Out of sync: start=147231992, size=1200 (sectors)
Dec 31 09:18:05 pro01 kernel: block drbd2: Out of sync: start=147233280, size=96 (sectors)
Dec 31 09:18:05 pro01 kernel: block drbd2: Out of sync: start=147233408, size=16 (sectors)
Dec 31 09:18:05 pro01 kernel: block drbd2: Out of sync: start=147233560, size=32 (sectors)
Dec 31 09:18:07 pro01 kernel: block drbd1: [drbd1_worker/20189] sock_sendmsg time expired, ko = 4294966911
Dec 31 09:18:09 pro01 kernel: block drbd2: Out of sync: start=147493960, size=8 (sectors)
Use in Global Configuration
syncer {
# rate after al-extents use-rle cpu-mask verify-alg csums-alg
verify-alg sha1;
rate 40M;
}
In each resource
resource r1 {
# kvm420
protocol C;
startup {
wfc-timeout 15; # non-zero wfc-timeout can be dangerous (http://forum.proxmox.com/threads/3465-Is-it-safe-to-use-wfc-timeout-in-DRBD-configuration)
degr-wfc-timeout 60;
}
net {
cram-hmac-alg sha1;
shared-secret "CDwCYfY7420s";
after-sb-0pri discard-zero-changes;
after-sb-1pri discard-secondary;
after-sb-2pri disconnect;
}
on pro01 {
device /dev/drbd1;
disk /dev/sata/vm-420-disk-1;
address XXX.XXX.XXX.XXX:7789;
meta-disk internal;
}
on pro02 {
device /dev/drbd1;
disk /dev/pve/vm-420-disk-1;
address XXX.XXX.XXX.XXX:7789;
meta-disk internal;
}
}
Nor do I understand correctly, if the execution of /sbin/drbdadm verify all errors are corrected.
Help is appreciated, as I am somewhat new to the suod and DRBD and I apologize for my English of Google translator.
A happy end of year...
resource r1 {
# kvm420
protocol C;
startup {
wfc-timeout 15; # non-zero wfc-timeout can be dangerous (http://forum.proxmox.com/threads/3465-Is-it-safe-to-use-wfc-timeout-in-DRBD-configuration)
degr-wfc-timeout 60;
}
net {
cram-hmac-alg sha1;
shared-secret "CDwCYfY7420s";
after-sb-0pri discard-zero-changes;
after-sb-1pri discard-secondary;
after-sb-2pri disconnect;
}
on pro01 {
device /dev/drbd1;
disk /dev/sata/vm-420-disk-1;
address XXX.XXX.XXX.XXX:7789;
meta-disk internal;
}
on pro02 {
device /dev/drbd1;
disk /dev/pve/vm-420-disk-1;
address XXX.XXX.XXX.XXX:7789;
meta-disk internal;
}
}
Abdelkarim Mateos Sánchez
CEO Tamainout Hébergement, S.A.R.L. (Marruecos)
CET Tamainut IT, S.L. (España)
Contacto | abkrim at tamainut.com | Skype - mamateos
Teléfono Fijo España: +34.851000209 | Marruecos Móvil: +212.671819412
islaserver.com | tamainut.tel
Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
This message is intended exclusively for its addresse and may contain information that is CONFIDENTIAL and protected by professional privilege. If you are not the intended recipient you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited by law. If this message has been received in error, please immediately notify us via e-mail and delete it.