HAST: split-brain -- how to force one side to become primary?

Freddie Cash fjwcash at gmail.com
Fri Mar 5 03:56:10 UTC 2010


On Thu, Mar 4, 2010 at 1:05 PM, Pawel Jakub Dawidek <pjd at freebsd.org> wrote:

> On Wed, Mar 03, 2010 at 04:31:40PM -0800, Freddie Cash wrote:
> > According to the wiki, when a split-brain situation arises, I should be
> able
> > to stop hastd on one side, write changes to the /dev/hast/* providers on
> the
> > primary to increment the localcnt valye, and then bring up the secondary
> > hastd.  The locacnt/remotecnt values will be different, and everything
> will
> > start to re-sync.
> >
> > However, this doesn't seem to work.  Or, maybe I'm not doing things right
> to
> > make it work.  Or maybe I've completely misunderstood how it all works.
> >  (Nah, that can never happen.  roll-eyes)  :)
>
> On split-brain, when you decide that you don't need data on one of the
> nodes you simply do the following on this node:
>
>        # hastctl role init <resource>
>        # hastctl create <resource>
>        # hastctl role secondary <resource>
>
>
I figured it would be something simple like that.  Thanks for the pointers.

I'll give this a try in a couple of weeks, when we're back from vacation.
:)

-- 
Freddie Cash
fjwcash at gmail.com


More information about the freebsd-fs mailing list