From owner-freebsd-fs@freebsd.org Thu Aug 11 10:15:45 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 D7A11BB0158 for ; Thu, 11 Aug 2016 10:15:45 +0000 (UTC) (envelope-from julien@perdition.city) Received: from relay-b03.edpnet.be (relay-b03.edpnet.be [212.71.1.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "edpnet.email", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7FDCE1DE4 for ; Thu, 11 Aug 2016 10:15:45 +0000 (UTC) (envelope-from julien@perdition.city) X-ASG-Debug-ID: 1470910540-0a88181ce524934a0001-3nHGF7 Received: from mordor.lan (213.211.139.72.dyn.edpnet.net [213.211.139.72]) by relay-b03.edpnet.be with ESMTP id jZy0ZZjshFt2Le5J (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 11 Aug 2016 12:15:41 +0200 (CEST) X-Barracuda-Envelope-From: julien@perdition.city X-Barracuda-Effective-Source-IP: 213.211.139.72.dyn.edpnet.net[213.211.139.72] X-Barracuda-Apparent-Source-IP: 213.211.139.72 Date: Thu, 11 Aug 2016 12:15:39 +0200 From: Julien Cigar To: Borja Marcos Cc: Jordan Hubbard , freebsd-fs@freebsd.org Subject: Re: HAST + ZFS + NFS + CARP Message-ID: <20160811101539.GM70364@mordor.lan> X-ASG-Orig-Subj: Re: HAST + ZFS + NFS + CARP References: <20160703214723.GF41276@mordor.lan> <65906F84-CFFC-40E9-8236-56AFB6BE2DE1@ixsystems.com> <61283600-A41A-4A8A-92F9-7FAFF54DD175@ixsystems.com> <20160704183643.GI41276@mordor.lan> <20160704193131.GJ41276@mordor.lan> <20160811091016.GI70364@mordor.lan> <1AA52221-9B04-4CF6-97A3-D2C2B330B7F9@sarenet.es> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="aiCxlS1GuupXjEh3" Content-Disposition: inline In-Reply-To: <1AA52221-9B04-4CF6-97A3-D2C2B330B7F9@sarenet.es> User-Agent: Mutt/1.6.1 (2016-04-27) X-Barracuda-Connect: 213.211.139.72.dyn.edpnet.net[213.211.139.72] X-Barracuda-Start-Time: 1470910540 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://212.71.1.220:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 2203 X-Virus-Scanned: by bsmtpd at edpnet.be X-Barracuda-BRTS-Status: 1 X-Barracuda-Bayes: INNOCENT GLOBAL 0.5000 1.0000 0.0100 X-Barracuda-Spam-Score: 0.01 X-Barracuda-Spam-Status: No, SCORE=0.01 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.31929 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 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: Thu, 11 Aug 2016 10:15:45 -0000 --aiCxlS1GuupXjEh3 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 11, 2016 at 11:24:40AM +0200, Borja Marcos wrote: >=20 > > On 11 Aug 2016, at 11:10, Julien Cigar wrote: > >=20 > > As I said in a previous post I tested the zfs send/receive approach (wi= th > > zrep) and it works (more or less) perfectly.. so I concur in all what y= ou > > said, especially about off-site replicate and synchronous replication. > >=20 > > Out of curiosity I'm also testing a ZFS + iSCSI + CARP at the moment,= =20 > > I'm in the early tests, haven't done any heavy writes yet, but ATM it= =20 > > works as expected, I havent' managed to corrupt the zpool. >=20 > I must be too old school, but I don=E2=80=99t quite like the idea of usin= g an essentially unreliable transport > (Ethernet) for low-level filesystem operations. >=20 > In case something went wrong, that approach could risk corrupting a pool.= Although, frankly, Yeah.. although you could have silent data corruption with any broken hardware too. Some years ago I suffered a silent data corruption due to=20 a broken RAID card, and had to restore from backups.. > ZFS is extremely resilient. One of mine even survived a SAS HBA problem t= hat caused some > silent corruption. Yep, and I would certainly not use another FS to do that. Scrubbing the pool more regularly is also something to do. >=20 > The advantage of ZFS send/receive of datasets is, however, that you can c= onsider it > essentially atomic. A transport corruption should not cause trouble (apar= t from a failed > "zfs receive") and with snapshot retention you can even roll back. You ca= n=E2=80=99t roll back > zpool replications :) >=20 > ZFS receive does a lot of sanity checks as well. As long as your zfs rece= ive doesn=E2=80=99t involve a rollback > to the latest snapshot, it won=E2=80=99t destroy anything by mistake. Jus= t make sure that your replica datasets > aren=E2=80=99t mounted and zfs receive won=E2=80=99t complain. >=20 >=20 > Cheers, >=20 >=20 >=20 >=20 > Borja. >=20 >=20 >=20 --=20 Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. --aiCxlS1GuupXjEh3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCgAGBQJXrFBIAAoJELK7NxCiBCPA5JsQAMOTJhdRd+NhiuSe3tggOkHb ZGZfaCuTPLsTg2enL7iFNpV2HIT9guiE88cZzr7tB5GGwJtIVT/JBZ3tkKbLo4bu +v82RbZxEDR8XhJPPtDM6mziqIuIMzhoya03LqrDW1BKhOPM3wBCYXSZj6TW15gZ ++koMV1QQzCOku8tjzG0yLbuDZ5q1fpadq9EfIV/4B10d/O3kfYilr500Lagc9x2 bNU0j5u+MwAr3lQjXtgfhg34YM7TAAS8vIJM1AzFKC9Sh6WKANOOJ2xWLkQVg583 LOSdhQ8LF+gwSQMPkDSnGYyvLw6pBaxQQZQDOT+V9bOY+r7zfOXuMWObO9LcM5r5 hT6J5xpIbs4y1uoPjmFSudbZ0oiQ9C8XR60W2tzTBPatgCc/s5zurz1iYwbIIR9C r34jUcRSYJd9gVHRhDdrBt3Pxb/kifaGAgbaZwRudSij51ynmADwYcJvY9evYdOF qkjPYtJNvETBSisWJs2Y/qTuYLmZl1n8n8jqS8pHwCtAAt7rBPHtZGwek41E6n59 7TWDmmt3XiFz4kTfDw8RErsP8c4TJo5VDbDJVdOQCwDBWuiP8o1BzG6tjNi/tF+W qVwoWL16vi2Qt4frDvcSiPCDzQVqdp7qLIgYpmzUh91Rd6LRQ3HFI+sIz+Cs9AyU rkQIvybQBCVqiYPN3EKC =e1vn -----END PGP SIGNATURE----- --aiCxlS1GuupXjEh3--