From owner-freebsd-fs@freebsd.org Tue Apr 24 11:04:35 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B66FF89D50 for ; Tue, 24 Apr 2018 11:04:35 +0000 (UTC) (envelope-from karli@inparadise.se) Received: from mail.inparadise.se (h-112-105.A444.priv.bahnhof.se [158.174.112.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DC2298276E for ; Tue, 24 Apr 2018 11:04:34 +0000 (UTC) (envelope-from karli@inparadise.se) Received: from localhost (localhost [127.0.0.1]) by mail.inparadise.se (Postfix) with ESMTP id 28D72431E9; Tue, 24 Apr 2018 13:04:33 +0200 (CEST) Received: from mail.inparadise.se ([127.0.0.1]) by localhost (mail.inparadise.se [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id MSd7xfvmqKGg; Tue, 24 Apr 2018 13:04:32 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.inparadise.se (Postfix) with ESMTP id 09C3B431F0; Tue, 24 Apr 2018 13:04:32 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.inparadise.se 09C3B431F0 X-Virus-Scanned: amavisd-new at inparadise.se Received: from mail.inparadise.se ([127.0.0.1]) by localhost (mail.inparadise.se [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id bGAlNz5nfUFW; Tue, 24 Apr 2018 13:04:31 +0200 (CEST) Received: from its-5cg60227mj (its-5cg60227mj.its.uu.se [130.238.131.18]) by mail.inparadise.se (Postfix) with ESMTPSA id E83CB431E9; Tue, 24 Apr 2018 13:04:30 +0200 (CEST) Message-ID: <1524567842.9560.66.camel@inparadise.se> Subject: Re: ctl_isc_lun_sync: Received conflicting HA LUN From: Karli =?ISO-8859-1?Q?Sj=F6berg?= Reply-To: karli@inparadise.se To: Mikhail Zakharov Cc: "freebsd-fs@freebsd.org" Date: Tue, 24 Apr 2018 13:04:02 +0200 In-Reply-To: <1524567621.9560.65.camel@inparadise.se> References: <4cb4aa83-bd49-0c20-4e41-c11c682b0570@sentex.net> <1e1e7cd5-0797-c168-fbce-a36edc6a432e@sentex.net> <1524550160.1130.6.camel@inparadise.se> <615DFFBB-239A-4350-B961-FD10D0C9A8DD@yahoo.com> <1524567621.9560.65.camel@inparadise.se> Organization: InParadise Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-PWWqx37QHYO2cefLF1q8" X-Mailer: Evolution 3.26.1-1 Mime-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2018 11:04:35 -0000 --=-PWWqx37QHYO2cefLF1q8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2018-04-24 at 13:00 +0200, Karli Sj=C3=B6berg via freebsd-fs wrote: > On Tue, 2018-04-24 at 12:32 +0300, Mikhail Zakharov wrote: > > Hi Karli, > >=20 > > Thank you, I=E2=80=99m just exploring the storage abilities of my prefe= rred > > OS - FreeBSD.=20 > >=20 > > Three nodes are preferable to choose the quorum for sure, but my > > idea > > was not to establish contacts between nodes. Instead of it, BQ uses > > a > > small partition for the =E2=80=9Cquorum=E2=80=9D on the same space wher= e data > > volume > > is located.=20 >=20 > Yes, of course. But there=C2=B4s nothing you from having three nodes 's/nothing you/nothing stopping you/' > connected to the same partition and being able to make more accurate > choices on when to take over? >=20 > If one node stops updating stamps, take over. If two nodes stops > updating, then the problem is likely network-related and _must not_ > take over to avoid split brain. Something like that? >=20 > /K >=20 > > And if a node looses access to the quorum it means, it looses > > access > > to the data volume too. Now, BQ runs on both nodes and both BQ > > instances write stamps to the quorum partition. If for any reason > > BQ > > on one node detects, the other node stops updating it=E2=80=99s stamps,= it > > performs failover procedure. It=E2=80=99s quite a questionable, rude wa= y, I > > can agree, and that=E2=80=99s why I always write a warning to use the B= eaST > > for testing only purposes.=20 > >=20 > > Best regards, > > Mike > >=20 > > > 24 =D0=B0=D0=BF=D1=80. 2018 =D0=B3., =D0=B2 9:09, Karli Sj=C3=B6berg = > > > =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0): > > >=20 > > > > On Mon, 2018-04-23 at 13:11 -0400, Mike Tancsa wrote: > > > > > On 4/23/2018 12:59 PM, Mikhail Zakharov wrote: > > > > >=20 > > > > > Hello Mike, > > > > >=20 > > > > > Thank you for your interest to my paper. I appreciate it very > > > > > much! > > > > > Your error may be a consequence of the initial HA > > > > > misconfiguration. > > > > > What is in your /boot/loader.conf? Although the described > > > > > config is > > > > > quite simple, I can recheck the instruction in my paper in a > > > > > couple > > > > > of weeks only, unfortunately I=E2=80=99m on vacation right now. > > >=20 > > > [snip] > > >=20 > > > I read your articles on CTL HA, BQ and BeaST, and just wanted to > > > say > > > they are amazing, good job! > > >=20 > > > One thing I=C2=B4m wondering about though is if you can claim HA with > > > just > > > two nodes, usually you need at least three, where the third is a > > > tie- > > > breaker. Otherwise with your current setup, both systems may > > > loose > > > contact with each other while both still being powered on, > > > leading > > > to > > > potential split brain situations. What are your thoughts about > > > that? > > >=20 > > > /K --=-PWWqx37QHYO2cefLF1q8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQEcBAABCAAGBQJa3w8iAAoJEBpo164N2cuRlWUIAIBoZTRb3CxKi9My7V+3+2Ca Wac9y1RvOpKAyUo77s+bvUhkfxMeHyFXUkRsvlVbW9rZqWSPYO4GfLAi4EBYMxYL O1PVt7Ks+0ASGbaL2ztGtoaqOuXCRkUl81YYdtO8loEGC1ipKs41FZjSdhV80z9K o1PvQ2T8/Jgq+inpzc1fNfvadgMO69VjiVCJo/lDk/FJhTQUwyADOUsXOiSdcP2z dxp8PtJPmm/h73MvctOgwT1JmkcpG6UDecPqF2ZINH2usxAdIrzuAVTnsQb+KxLg r3WP9/uay4KonceUiesErTLBfA3slTCjJN3dR82ujKw2mQXs9Y5czZOy15W23VM= =vuBA -----END PGP SIGNATURE----- --=-PWWqx37QHYO2cefLF1q8--