brchrisman at gmail
May 10, 2012, 7:17 PM
Post #3 of 3
On Mon, Apr 30, 2012 at 5:32 AM, Lars Ellenberg
Re: when does 'drbdadm wait-connect all' return?
[In reply to]
<lars.ellenberg [at] linbit>wrote:
> On Tue, Apr 24, 2012 at 11:42:10AM -0700, Brian Chrisman wrote:
> > Documentation drbdadm is ambiguous here:
> > "Waits until the device is connected to its peer device."
> > .. because the phrase 'the device' implies a single device.
> > In such a case as 'drbdadm wait-connect all', I would assume that the
> > command returns when all devices have connected but wanted to verify that
> > is the case.
> wait-connect returns when
> either the connection handshake was successfull, and
> connection state is now "Connected" or one of the Sync states,
> or the resource went into "StandAlone"
> unless you wait-connect with "--wait-after-sb",
> or the wait timeout expired.
> drbdadm whatever all
> calls the respective drbdmeta or drbdsetup command
> for all resources in turn.
> so drbdadm wait-connect all would return after all individual drbdsetup
> wait-connect exited, for whatever reason, and of course there is no
> guarantee that those that connected first are really still connected
> when the last drbdsetup exits.
> Did that help at all?
That is what I hoped it meant. Thanks for the clarification.
> : Lars Ellenberg
> : LINBIT | Your Way to High Availability
> : DRBD/HA support and consulting http://www.linbit.com
> DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
> please don't Cc me, but send to list -- I'm subscribed
> drbd-user mailing list
> drbd-user [at] lists