Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Lars Ellenberg <Lars.Ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] About the UUID
Date: Wed, 20 Dec 2006 09:40:22 +0100	[thread overview]
Message-ID: <20061220084022.GA8110@soda.linbit> (raw)
In-Reply-To: <4588E111.8090102@163.com>

/ 2006-12-20 15:06:57 +0800
\ home_king:
> hi, Philipp.
> 
> Now drbd-0.8.x uses UUID instead of GC as the data-relationship-detection
> -tool, right? Its logic seems clearer than GC. However, I am confused
> about the UUID in the two-primaries-healedpartition scenario.
> 
> Given the original uuids below (both nodes are connected):
> P <5,0,0,0>      S <5,0,0,0>
> then, I plug out the wire of the primary node (disconnected):
> P <6,5,0,0>      S <5,0,0,0>
> I let the downgraded secondary become new primary, UUID should become:
> P <6,5,0,0>      S <6,5,0,0>

no. these small digits are only more readable examples.
our UUIDs are 63bit random numbers.
they may clash, and we have to fix that somewhen.
but that is not very likely.

we probably should change the example to read more like
head -c8 /dev/urandom | hd
<3cecd7aed66ff5ad,0,0,0>		<3cecd7aed66ff5ad,0,0,0>
<dc855810336641b6,3cecd7aed66ff5ad,0,0>	<3cecd7aed66ff5ad,0,0,0>
<dc855810336641b6,3cecd7aed66ff5ad,0,0>	<44dc24617bd63967,3cecd7aed66ff5ad,0,0>

to make this more obvious.

> BTW, I did not test such scenario, because I can't compile drbd-0.8.x
> in my RedHat AS4 distro.

works for me.

-- 
: Lars Ellenberg                            Tel +43-1-8178292-55 :
: LINBIT Information Technologies GmbH      Fax +43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe    http://www.linbit.com :

      reply	other threads:[~2006-12-20  8:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20  7:06 [Drbd-dev] About the UUID home_king
2006-12-20  8:40 ` Lars Ellenberg [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061220084022.GA8110@soda.linbit \
    --to=lars.ellenberg@linbit.com \
    --cc=drbd-dev@lists.linbit.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox