<meta content="text/html; charset=ISO-8859-1"
<body bgcolor="#FFFFFF" text="#000000">
<font size="-1"><font face="Cambria">This was 100% spot on the
answer I was looking for- thanks guys!<br>
Also, do any white papers exist on how DRBD works on the inside?
From what you told me it looks like its <br>
Write to DRBD Block Device -> Write to TCP buffer -> Write
to host disks<br>
I thought it was<br>
Write DRBD Block Device -> Write to disk -> Write to TCP
Buffer -> Write to host disks (like a push method almost)<br>
Which is why I wanted to know about disk corruption but from
what it seems like is that I should be more concerned about
corruption in the network stack, right?<br>
<div class="moz-signature"><font size="2">
<i>Lead Infrastructure & Systems Administrator</i><br>
<b>Office</b>: 1-646-290-6267 | <b>Mobile</b>: 1-646-385-3684<br>
Notice to Recipient: This e-mail is meant only for the intended
recipient(s) of the transmission, and contains confidential
information which is proprietary<br>
to FIX Flyer LLC. Any unauthorized use, copying, distribution,
or dissemination is strictly prohibited. All rights to this
information is reserved by FIX Flyer LLC.<br>
If you are not the intended recipient, please contact the sender
by reply e-mail and please delete this e-mail from your system
and destroy any copies<br>
On 10/12/2011 3:04 AM, Florian Haas wrote:
<blockquote cite="mid:4E953C08.firstname.lastname@example.org" type="cite">
<pre wrap="">On 2011-10-11 17:09, Charles Kozler wrote:
I have been reading the docs and still seem to be unclear as to some things-
Assume I have a two node setup with DRBD in Primary/Primary with Xen
writing to /dev/drbd0 on node1. I use Primary/Primary for live migration
and in my Xen DomU configuration file I use phy: and not drbd: handler.
Now, what happens if the disk on node1 begins to fail and the blocks
where /dev/drbd0 resides are corrupted while we continue to write to
this- will these bad/corrupted blocks be replicated to node2?
If the underlying _disk_ fails in weird ways and that is why you get
corruption, then the corruption occurs below the DRBD level and there's
no corruption for DRBD to replicate.
If however you have one of your Xen domUs writing garbage to that device
(so the corruption occurs in a layer above DRBD), then of course DRBD
will happily replicate that corruption.
<pre wrap="">Example aside, in short, I am wondering if a failing disk on a node will
result in DRBD replicating bad block data to the secondary node. I know
there a place in the docs describing integrity checker using the kernels
crypt algo's (like md5) so maybe thats an option to prevent it?
Nope, that will only prevent corruption that may occur *within* DRBD due
to a fishy network layer, or bit flips on your PCI bus, or broken
checksum offloading on your NICs.
For preventing corruption in the disk I/O layer, DRBD would have to
support DIF/DIX, which it currently doesn't do (very few applications do).
<pre wrap="">In either case, is there any way to prevent bad block data from node 1
being replicated to node 2?
Corruption rooted in the network stack, yes -- use data-integrity-alg.
Corruption rooted in your Xen domU, nope.
For corruption rooted in the I/O layer, you can't prevent the
replication from happening but you can detect the corruption after the
fact -- use verify-alg and run device verification.
Hope this helps,