Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Cc: "Montrose, Ernest" <Ernest.Montrose@stratus.com>
Subject: Re: [Drbd-dev] drbdsetup  events patch to announce Split-brain
Date: Thu, 25 Oct 2007 12:15:46 +0200	[thread overview]
Message-ID: <200710251215.47192.philipp.reisner@linbit.com> (raw)
In-Reply-To: <BD7042533C2F8943A6A4257A9E31C454F479FA@EXNA.corp.stratus.com>

On Monday 01 October 2007 23:24:02 Montrose, Ernest wrote:
> Hi,
>
> Included here is a small patch that I find useful when monitoring with
> drbdsetup().  It adds the ability to generate an netlink event to user
> space when drbd Split-brain and disconnect.  Based on that event we can
> then take action. I could not find a more
> convenient way to know that a split-brain occurred other then looking in
> /var/log/messages.
>

Hi Ernest,

I have nearly overlooked this patch... 
You are right, it is definitely a good idea to have that. 

I just need to change the tag number for the split_brain flag,
since that number is already allocated in drbd-8.2.0. 

The question I have, what is the flag good for ? Do you envision
an future use of it ?  otherwise I would drop it, it is possible
to have such an cn packet, that does not carry any futher data...

-phil
-- 
: Dipl-Ing Philipp Reisner                      Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH          Fax +43-1-8178292-82 :
: Vivenotgasse 48, 1120 Vienna, Austria        http://www.linbit.com :

  reply	other threads:[~2007-10-25 10:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01 21:24 [Drbd-dev] drbdsetup events patch to announce Split-brain Montrose, Ernest
2007-10-25 10:15 ` Philipp Reisner [this message]
2007-10-25 12:24 ` Montrose, Ernest
2007-10-29 10:19   ` Philipp Reisner
2007-10-29 13:36   ` Montrose, Ernest

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=200710251215.47192.philipp.reisner@linbit.com \
    --to=philipp.reisner@linbit.com \
    --cc=Ernest.Montrose@stratus.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