From owner-freebsd-fs@freebsd.org Fri Jul 1 09:42:19 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12B8AB88F7A for ; Fri, 1 Jul 2016 09:42:19 +0000 (UTC) (envelope-from jg@internetx.com) Received: from mx1.internetx.com (mx1.internetx.com [62.116.129.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CB1B6224E for ; Fri, 1 Jul 2016 09:42:18 +0000 (UTC) (envelope-from jg@internetx.com) Received: from localhost (localhost [127.0.0.1]) by mx1.internetx.com (Postfix) with ESMTP id C79C945FC0E4; Fri, 1 Jul 2016 11:42:15 +0200 (CEST) X-Virus-Scanned: InterNetX GmbH amavisd-new at ix-mailer.internetx.de Received: from mx1.internetx.com ([62.116.129.39]) by localhost (ix-mailer.internetx.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CzIXECtz2mKi; Fri, 1 Jul 2016 11:42:13 +0200 (CEST) Received: from [192.168.100.26] (pizza.internetx.de [62.116.129.3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.internetx.com (Postfix) with ESMTPSA id 706F745FC0E5; Fri, 1 Jul 2016 11:42:13 +0200 (CEST) Subject: Re: HAST + ZFS + NFS + CARP References: <20160630144546.GB99997@mordor.lan> <71b8da1e-acb2-9d4e-5d11-20695aa5274a@internetx.com> <20160630153747.GB5695@mordor.lan> <63C07474-BDD5-42AA-BF4A-85A0E04D3CC2@gmail.com> <20160630163541.GC5695@mordor.lan> <50BF1AEF-3ECC-4C30-B8E1-678E02735BB5@gmail.com> <20160701084717.GE5695@mordor.lan> To: Julien Cigar , Ben RUBSON Cc: freebsd-fs@freebsd.org Reply-To: jg@internetx.com From: InterNetX - Juergen Gotteswinter Message-ID: <47c7e1a5-6ae8-689c-9c2d-bb92f659ea43@internetx.com> Date: Fri, 1 Jul 2016 11:42:13 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <20160701084717.GE5695@mordor.lan> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 09:42:19 -0000 > > Thank you very much for those "advices", it is much appreciated! > > I'll definitively go with iSCSI (for which I haven't that much > experience) over HAST. good luck, i rather cut one of my fingers than using something like this in production. but its probably a quick way if one targets to find a new opportunity ;) > > Maybe a stupid question but, assuming on the MASTER with ada{0,1} the > local disks and da{0,1} the exported iSCSI disks from the SLAVE, would > you go with: > > $> zpool create storage mirror /dev/ada0s1 /dev/ada1s1 mirror /dev/da0 > /dev/da1 > > or rather: > > $> zpool create storage mirror /dev/ada0s1 /dev/da0 mirror /dev/ada1s1 > /dev/da1 > > I guess the former is better, but it's just to be sure .. (or maybe it's > better to iSCSI export a ZVOL from the SLAVE?) > are you really sure you understand what you trying to do? even if its currently so, i bet in a desaster case you will be lost. > Correct me if I'm wrong but, from a safety point of view this setup is > also the safest as you'll get the "fullsync" equivalent mode of HAST > (but but it's also the slowest), so I can be 99,99% confident that the > pool on the SLAVE will never be corrupted, even in the case where the > MASTER suddently die (power outage, etc), and that a zpool import -f > storage will always work? 99,99% ? optimistic, very optimistic. we are playing with recovery of a test pool which has been imported on two nodes at the same time. looks pretty messy > > One last thing: this "storage" pool will be exported through NFS on the > clients, and when a failover occur they should, in theory, not notice > it. I know that it's pretty hypothetical but I wondered if pfsync could > play a role in this area (active connections)..? > they will notice, and they will stuck or worse (reboot) > Thanks! > Julien > >> >>>>>> ZFS would then know as soon as a disk is failing. >>>>>> And if the master fails, you only have to import (-f certainly, in case of a master power failure) on the slave. >>>>>> >>>>>> Ben >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >