RE: DRBD8: Fencing and outdate-peer handler getting calledmultiple times

Lars,
Aha! Thanks for the clarification. I will try again.

EM--

-----Original Message-----
From: drbd-dev-bounces-63ez5xqkn6DQT0dZR+AlfA@xxxxxxxxxxxxxxxx 
[mailto:drbd-dev-bounces-63ez5xqkn6DQT0dZR+AlfA@xxxxxxxxxxxxxxxx]
On Behalf Of Lars Ellenberg
Sent: Friday, November 17, 2006 9:13 AM
To: drbd-dev-63ez5xqkn6DQT0dZR+AlfA@xxxxxxxxxxxxxxxx
Subject: Re: [Drbd-dev] DRBD8: Fencing and outdate-peer handler getting
calledmultiple times

/ 2006-11-16 08:10:56 -0500
\ Montrose, Ernest:
> Phil,
> My outdate-peer handler simply says "echo /deve/drbd0: Running handler
for outdate-peer >>/tmp/drbdio.log"
> And that log file is populated and created so I can only assume that
did indicate success.
> In this case success being an exit status of 0.

and exactly that assumption is wrong.

in your kernel log you should find messages like
"outdate-peer helper broken, returned 0" 

>   If the disk state of the peer is unknown, drbd calls this 
>   handler (yes a call to userspace from kernel space). The handler's
>   returncodes are:
> 
>   3 -> peer is inconsistent 
>   4 -> peer is outdated (this handler outdated it) [ resource fencing
]
>   5 -> peer was down / unreachable
>   6 -> peer is primary
>   7 -> peer got stonithed [ node fencing ]

these are the only valid return codes.

"success" being defined as 
  "was able to outdate the peer" respective
  "peer need not to be outdated"

-- 
: Lars Ellenberg                                  Tel +43-1-8178292-55 :
: LINBIT Information Technologies GmbH            Fax +43-1-8178292-82 :
: Schoenbrunner Str. 244, A-1120 Vienna/Europe   http://www.linbit.com :
_______________________________________________
drbd-dev mailing list
drbd-dev-cunTk1MwBs8qoQakbn7OcQ@xxxxxxxxxxxxxxxx
http://lists.linbit.com/mailman/listinfo/drbd-dev