From owner-freebsd-fs@FreeBSD.ORG Mon Jul 5 19:27:01 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 854831065670 for ; Mon, 5 Jul 2010 19:27:01 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 431CC8FC17 for ; Mon, 5 Jul 2010 19:27:01 +0000 (UTC) Received: by iwn35 with SMTP id 35so4194706iwn.13 for ; Mon, 05 Jul 2010 12:27:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=XNwxRL/gWfNOQOev3e8AhgfrPUlHyOReOy7zNucyXuc=; b=XLMliJ8bQXqONXBDVs2QrdV7gpRYyAXGoRsXAUZ02aOhcS3CR5eJx0nPKWDrFJqS98 OU1lM726ildCWuhvZpkg6zQAV3YC3ZpdvGAaTCwZ6hAW8anP/xBcXsIS/Muj18FITXS8 x1nOY6aehhfCI4Er/A/1r6rnDg8TbQ9HuQUA4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=UFQmKonnJWFHcBiJ322Dgp+Wz6OD0ehtnnX+0e1fX8rACkqRXGgn9E/QdrxjADrZHt qPgUxIL5CwDa12hyrvaSUoi6mMmB1uFmmhOWRAVkn4L+7pverTkyK5/ozIb/adqRGM21 dky0FD8QWw7gHeg5LLWKAiIYZDBaj+/jP6IQ4= MIME-Version: 1.0 Received: by 10.231.146.129 with SMTP id h1mr3434181ibv.181.1278358020738; Mon, 05 Jul 2010 12:27:00 -0700 (PDT) Received: by 10.231.37.11 with HTTP; Mon, 5 Jul 2010 12:27:00 -0700 (PDT) In-Reply-To: <4C31681C.5070406@soupacific.com> 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> Date: Mon, 5 Jul 2010 12:27:00 -0700 Message-ID: From: Freddie Cash To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 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 19:27:01 -0000 On Sun, Jul 4, 2010 at 10:05 PM, hiroshi@soupacific.com wrote: >> I think you could make a configuration so when hostB (secondary) switches >> to master it changes advskew to the value lower then on hostA. > >> In this way after hostA reboot it will have higher advskew and will be forced to do as a >> secondary. Then after the nodes are synchronized you can switch to the >> initial state restoring initial value of advskew on hostB. >> > NO ! Once split-brain mode appeared, CARP and HAST as BACKUP mode by changed > whatever, advskew value etc. No way to get out slip-brain complain forever! > > Is there anybody having same problem ? Only me? 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. 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.) -- Freddie Cash fjwcash@gmail.com