From owner-freebsd-fs@FreeBSD.ORG Mon Jul 5 23:04:23 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E13601065672 for ; Mon, 5 Jul 2010 23:04:23 +0000 (UTC) (envelope-from hiroshi@soupacific.com) Received: from mail.soupacific.com (mail.soupacific.com [211.19.53.201]) by mx1.freebsd.org (Postfix) with ESMTP id A8A728FC0A for ; Mon, 5 Jul 2010 23:04:23 +0000 (UTC) Received: from [127.0.0.1] (unknown [192.168.1.239]) by mail.soupacific.com (Postfix) with ESMTP id AF4636CFC8 for ; Mon, 5 Jul 2010 22:56:22 +0000 (UTC) Message-ID: <4C3264F5.1090700@soupacific.com> Date: Tue, 06 Jul 2010 08:04:21 +0900 From: "hiroshi@soupacific.com" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4C139F9C.2090305@soupacific.com> <86iq5oc82y.fsf@kopusha.home.net><4C14215D.9090304@soupacific.com><20100613003635.GA60012@icarus.home.lan><20100613074921.GB1320@garage.freebsd.pl><4C149A5C.3070401@soupacific.com><20100613102401.GE1320@garage.freebsd.pl><86eigavzsg.fsf@kopusha.home.net><20100614095044.GH1721@garage.freebsd.pl><868w6hwt2w.fsf@kopusha.home.net><20100614153746.GN1721@garage.freebsd.pl><86zkyxvc4v.fsf@kopusha.home.net> <4C2C43D5.1080907@soupacific.com><86mxubndrp.fsf@kopusha.home.net> <4C2D7615.5070606@soupacific.com><861vbm1hpr.fsf@zhuzha.ua1> <4C2D9C62.4050105@soupacific.com><86wrtez14z.fsf@zhuzha.ua1> <4C2DC801.5080108@soupacific.com><86iq4xx9fy.fsf@kopusha.home.net> <4C2F3E14.1080601@soupacific.com><86pqz3iw33.fsf@kopusha.home.net> <4C31681C.5070406@soupacific.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: HAST and CARP X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2010 23:04:24 -0000 HI ! > Once you are in a split-brain situation, you have to take manual steps > to repair. > > Set one side as master. > > Then run "hastctl create" on the other box, to reset all the hast > metadata on the devices, and initiate a new sync from the master. > That's I understand. hstctl create xxx and hastctl -f role secondary xxx are almost same manner. > Ideally, any automated scripts would handle all the possible error > conditions and checks, and prevent the systems from getting into the > split-brain situation in the first place. :) (Yeah, a lot easier > said than done.) Other side can only know MASTER was dead, but MASTER once dead, how can MASTER know he is already dead ? Conclusion is once split-brain happen, DO hastctl create xxx. Thanks Hiroshi