From owner-freebsd-fs@freebsd.org Mon Sep 21 21:10:21 2015 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 100F4A06F0F for ; Mon, 21 Sep 2015 21:10:21 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (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 B12261777 for ; Mon, 21 Sep 2015 21:10:20 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by wiclk2 with SMTP id lk2so130215708wic.1 for ; Mon, 21 Sep 2015 14:10:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=KAEBsAQRCo9sP4NTUR6U207GT+4Kzq+LRDIcFFoIVBw=; b=m1+wB2I6Ik35H9c6ArgsVtDWqORowBeL0Ab8RcuEmNZEGoPgOkmPZp3gCubjcOKXD/ qYLqiU5wDKaKs9TNxb1JfnXrmVyKgOXsQ6A4UIHHmgbKvWBGUwkddgUrIwsD/Dyh3SZK 3/xA33PhWKJmCjPXAH5ZH7KyN6LPfXKZ3UGr/LkF+DwMTyqbYtRQU5ujrvDG6O18i7Mp po18qVZD+FCGINZP4I+UUrvnymBiYtVyI05WlQkGs9sxMcW+WZMLCVM1rX4ZK4s48VyY OPMGLBV5D3hy8fD1gsPkb6yslRIS4V8BXm5u3BszcmG9dqG4HP/B+zhR11FSNUY2W9hy uXSw== X-Received: by 10.180.186.10 with SMTP id fg10mr16005023wic.30.1442869818206; Mon, 21 Sep 2015 14:10:18 -0700 (PDT) Received: from [192.168.0.139] (cag06-2-82-237-68-117.fbx.proxad.net. [82.237.68.117]) by smtp.gmail.com with ESMTPSA id pl7sm15401297wic.4.2015.09.21.14.10.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Sep 2015 14:10:17 -0700 (PDT) From: Ben RUBSON Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: [HAST] ZFS, many disks, write order Message-Id: Date: Mon, 21 Sep 2015 23:10:15 +0200 To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 21:10:21 -0000 Hello, I plan to use HAST to synchronize a ZFS pool between 2 servers. The ZFS pool has 3 RAID-Z2 VDEVs (8+2), + 3 spares. +1 mirror for SLOG. +1 mirror for L2ARC. So a total of 37 disks (4TB each). 40Gb/s network bandwidth between the 2 servers. Will I have to define each of the 37 disks/resources in hast.conf ? Stupid question, but will this setup (with so many resources) work ? Will write IOs be ordered on the secondary node in the same order (over = all the 37 devices) as they occurred on the primary node ? This of course to have the secondary node consistent, even after a power = failure of the primary during a high IO load, leading into an import -F = on the secondary node. In HAST, each resource seems to be "independent" from the others. In DRBD, as an example, we can put several volumes in a same resource to = guarantee write order over all the volumes (disks) of the resource. Example : resource r0 { volume 0 { device /dev/drbd0; disk /dev/c0v0; } volume 1 { device /dev/drbd1; disk /dev/c0v1; } } What about HAST then ? Of course I would have liked to have my 37 disks as volumes in the same = resource, as in the example above. Thank you very much for your help ! Best regards, Ben