On Fri, Aug 04, 2017 at 10:31:02AM +0200, Jan Schermer wrote:
> I think it’s more likely he’s hitting a number of bugs that are
> getting fixed in DRBD, where it would simply not resync data while
> appearing Consistent/UpToDate etc.
No. This is a drbd8.4 setup and you are talking about drbd9.
AFAIK this should not affect data integrity at rest (related to “verify-alg”)
but only in-flight (csum-alg), and even then at most few blocks (that are
in-flight) should be affected? (btw shouldn’t stable_pages_required be enabled?)
I think it’s more likely he’s hitting a number of bugs that
Hi Luke,
I assume you are experiencing the results of data inconsistency by
in-flight writes. This means that a process (here your VM's qemu) can
change a block that already waits to be written to disk.
Whether this happens (undetected) or not depends on how the data is
accessed for writing and
Hello everyone.
I have a fairly simple 2-node CentOS 7 setup running KVM virtual
machines, with DRBD 8.4.9 between them.
There is one DRBD resource per VM, with at least 1 volume each,
totalling 47 volumes.
There's no clustering or heartbeat or other complexity. DRBD has it's
own Gig-E
Hello everyone.
I have a fairly simple 2-node CentOS 7 setup running KVM virtual machines,
with DRBD 8.4.9 between them.
There is one DRBD resource per VM, with at least 1 volume each, totalling
47 volumes.
There's no clustering or heartbeat or other complexity. DRBD has it's own
Gig-E
Hello everyone.
I have a fairly simple 2-node CentOS 7 setup running KVM virtual machines,
with DRBD 8.4.9 between them.
There is one DRBD resource per VM, with at least 1 volume each, totalling
47 volumes.
There's no clustering or heartbeat or other complexity. DRBD has it's own
Gig-E
