Date: Tue, 31 May 2016 14:49:30 -0700 From: Freddie Cash <fjwcash@gmail.com> To: "Eugene M. Zheganin" <emz@norma.perm.ru> Cc: stable@freebsd.org Subject: Re: HAST, zfs and local mirroring Message-ID: <CAOjFWZ5YOPPF=85NWTj7Uye-zqrCk5EbYjvGqfAoBJdJ37OiXA@mail.gmail.com> In-Reply-To: <bf4a004f-8c7f-1e2e-0c31-3de266975ae4@norma.perm.ru> References: <bf4a004f-8c7f-1e2e-0c31-3de266975ae4@norma.perm.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 31, 2016 at 11:18 AM, Eugene M. Zheganin <emz@norma.perm.ru> wrote: > I wat to start using HAST, I have two nodes and a pair of disk on each > node. So I want to use HASt in an environment where each HAST resource > would be mirrored. What is the preferred approach if I want to use ZFS on > an end-device to avoid exsessive fscking, and, in the same time, I want t= o > have some redundancy on a block level ? I see two possibility: HAST on a > zvol of a mirrored pool, and a ZFS on a hast. But recently I heard that > nested zfs (like zfs on zvol) is clamed unsupported. Futhermore, I have z= fs > on a geli on a zvol, and this solution proved itself to be very affected = to > livelocking - when disk i/o on a such fs is above some treshold, system i= s > locking, and the only way out is to reset it. Should I chose geom_mirror = to > provide a device for HAST and the build ZFS on it ? > =E2=80=8BThe generally recommend way to do this is to create a HAST resourc= e out of 1 disk from each system, and then build the ZFS pool using the HAST resources as the "disks". That way, your ZFS pool is made up of 2 HAST devices in a mirror vdev. And each of the two HAST devices uses one disk from each server (total of four disks). =E2=80=8B --=20 Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ5YOPPF=85NWTj7Uye-zqrCk5EbYjvGqfAoBJdJ37OiXA>