From owner-freebsd-fs@freebsd.org Tue May 17 10:30:16 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 83E92B3F0E9 for ; Tue, 17 May 2016 10:30:16 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C93B101F for ; Tue, 17 May 2016 10:30:16 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id a17so22804850wme.0 for ; Tue, 17 May 2016 03:30:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jty0ntpJDQGFhO9kRh3QxQ/7cIhmQo6O2TEo6JXUcD8=; b=NmWfhwGoZYPQv84VccOt96jk5ETqkdYM93eRba4g9TOf+tKUAHTP3mzu5PfGDeuqEy JA5Bs1pch0pMeG3ar8okJSje6sDq9SZWcRrutGmBpe1sD3IcfglKWF/kZ96+9ZySz2uC JSyE6FBRBvEkQ/MxnD2ZH5lfHf79hJb/UH9fE4yjfLRYza/eysQmZFdN18AvGZfX80Fo SkgsJGW7vUkpCCzwKAGLjJj6Cosnzb2vpCkPXocM2ts+gxwW65tD0PVJOnqgdJ4+WzG6 QPerm2DSeVgHnTlqYItPodXk1xNz65iyTfWTIEWDYyMyJ4FF0S7qeGSV4xVGOTadiuXw a61A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jty0ntpJDQGFhO9kRh3QxQ/7cIhmQo6O2TEo6JXUcD8=; b=abYT7RgQ8lNOwwg+ccy3y/br34uWppe0zu+a3pt9Fn8Yp88Kxy1g5dCbSjdTgHvfpx 3jHRaqXWFFzdooAMlHOgmkY2nsQifRuefQrtsfXp0/tc3Gn4GB5KZ1xumO9EJmPMTb9Z Tnj784wqiLnDvou8juSxorK0QwSIumARuXD1/f+ejN4TXECqJ+Ii+CEQfjH5FmvSzLZc jOJbLWwBjJIjirrhXkAixSbkyId4MHP9MbeUf+0pASEmeID99XnxlW76TPV42NknJlAV YXdPZYPAavEXN/3kkM+9xAsl9FJ+RPxkPXxVOWM10BSoTmuPWCBK8OHPQqy4WO4wM1Ko GVsA== X-Gm-Message-State: AOPr4FX4ft77QpFfUdSZUwLp5rkCsevvlXs07vLdnWJjRjuoH+WzqMBmTmzCbLcgyIYy5w== X-Received: by 10.194.72.103 with SMTP id c7mr646622wjv.65.1463481014764; Tue, 17 May 2016 03:30:14 -0700 (PDT) Received: from [192.168.1.16] (210.236.26.109.rev.sfr.net. [109.26.236.210]) by smtp.gmail.com with ESMTPSA id lr9sm2297152wjb.39.2016.05.17.03.30.13 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 17 May 2016 03:30:14 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Best practice for high availability ZFS pool From: Ben RUBSON In-Reply-To: Date: Tue, 17 May 2016 12:30:13 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <5E69742D-D2E0-437F-B4A9-A71508C370F9@FreeBSD.org> To: freebsd-fs@freebsd.org X-Mailer: Apple Mail (2.3124) 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: Tue, 17 May 2016 10:30:16 -0000 > On 17 may 2016 at 03:43, Bob Friesenhahn = wrote: >=20 > On Mon, 16 May 2016, Palle Girgensohn wrote: >>=20 >> Shared storage still has a single point of failure, the JBOD box. = Apart from that, is there even any support for the kind of storage PCI = cards that support dual head for a storage box? I cannot find any. >=20 > Use two (or three) JBOD boxes and do simple zfs mirroring across them = so you can unplug a JBOD and the pool still works. Or use a bunch of = JBOD boxes and use zfs raidz2 (or raidz3) across them with careful LUN = selection so there is total storage redundancy and you can unplug a JBOD = and the pool still works. >=20 > Fiber channel (or FCoE) or iSCSI allows putting the hardware at some = distance. >=20 > Without completely isolated systems there is always the risk of total = failure. Even with zfs send there is the risk of total failure if the = sent data results in corruption on the receiving side. In this case rollback one of the previous snapshots on the receiving = side ? Did you mean the sent data can totally brake the receiving pool making = it unusable / unable to import ? Did we already see this ? Thank you, Ben=