From: home_king <home_king@163.com>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] About the UUID
Date: Wed, 20 Dec 2006 15:06:57 +0800 [thread overview]
Message-ID: <4588E111.8090102@163.com> (raw)
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>
Finally, I recover the wire of primary. And Now, there comes my problem.
Accordding to the UUID algorithm, when Cs == Cp, no resynchronisation
necessary. However it is obviously split-brain, and drbd ignores it.
Why?
BTW, I did not test such scenario, because I can't compile drbd-0.8.x
in my RedHat AS4 distro. I just browsed the doc & code. :-)
Regards,
luo.jinhua
next reply other threads:[~2006-12-20 7:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 7:06 home_king [this message]
2006-12-20 8:40 ` [Drbd-dev] About the UUID Lars Ellenberg
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=4588E111.8090102@163.com \
--to=home_king@163.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