[DRBD-user] DRBD 0.7.23 and MD corruption

[Ross S. W. Walker]

> -----Original Message-----
> From: drbd-user-bounces at lists.linbit.com 
> [mailto:drbd-user-bounces at lists.linbit.com] On Behalf Of Lars 
> Ellenberg
> Sent: Thursday, May 24, 2007 5:01 AM
> To: drbd-user at lists.linbit.com
> Subject: Re: [DRBD-user] DRBD 0.7.23 and MD corruption
> 
> On Wed, May 23, 2007 at 01:04:05PM -0400, Ross S. W. Walker wrote:
> > I remember the performance issue with meta-data on raid1 
> and barriers
> > not being passed down.
> 
> it wasn't barriers (those are handled ok since ages),
> it was the "bio_sync" flag == queue unplug hint.
> 
> > Another thing, is there any plans to implement a many-to-many
> > replication topology with DRBD say utilizing multicasting?
> 
> sure.
> but the necessary state engine is not exactly trivial...
> 
> until then, you can sort-of daisy chain drbds,
> not automate anything and solve do the state engine
> in the operators brain.  or not.
>  :)

I don't know if this operator's brain is non-trivial enough for
that setup :^)

Yes, a many-to-many setup, which people will want to see as
multiple primaries, will be exceedingly difficult and complex as it
would no longer have the luxury of assumed 1-on-1 state transitions
and may have to deal with many different states transitioning at once.

Is there not already a practical example of such a system out there
already so wheels don't need to be re-invented?

-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.