[DRBD-user] "Concurrent local write detected!"

Dan Barker dbarker at visioncomm.net
Wed Dec 29 23:28:14 CET 2010

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

> From: drbd-user-bounces at lists.linbit.
> Sent: Wednesday, December 29, 2010 4:49 PM
> I really think drbd is being brain-dead here.  Concurrent writes to
> the same LBA aren't an issue... just do it!  Note the below is using a
> primary/secondary setup on two raw drbd devices; no GFS anywhere.


But the result is undefined! What should DRBD write to the other member? The
result of the first or the second write?

You are using a tool that permits the execution of stupid I/O streams. Good
for stress testing, but not good for data integrity. If you want undefined
data on a DRBD pair, then disconnect before the I/O, do the undefined thing,
and upon reconnect DRBD will faithfully replicate the garbage. It will still
be  undefined stuff, but it will be identical undefined stuff.

Dan in Atlanta 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4993 bytes
Desc: not available
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20101229/916b6d75/attachment.bin>

More information about the drbd-user mailing list