Date: Mon, 28 Mar 2011 13:52:45 +0300 From: Mikolaj Golub <trociny@freebsd.org> To: Pete French <petefrench@ingresso.co.uk> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, freebsd-current@freebsd.org, fjwcash@gmail.com, pjd@freebsd.org Subject: Re: Any success stories for HAST + ZFS? Message-ID: <86wrjj5xfm.fsf@in138.ua3> In-Reply-To: <E1Q492g-000CvZ-DI@dilbert.ticketswitch.com> (Pete French's message of "Mon, 28 Mar 2011 10:47:22 %2B0100") References: <E1Q492g-000CvZ-DI@dilbert.ticketswitch.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 28 Mar 2011 10:47:22 +0100 Pete French wrote: >> It is not a hastd crash, but a kernel crash triggered by hastd process. >> >> I am not sure I got the same crash as you but apparently the race is possible >> in g_gate on device creation. >> >> I got the following crash starting many hast providers simultaneously: PF> This is very interestng to me - my successful ZFS+HAST only had PF> a single drive, but in my new setup I am intending to use two PF> HAST processes and then mirror across thhem under ZFS, so I am PF> likely to hit this bug. Are the processes stable once launched ? Yes, you may hit it only on hast devices creation. The workaround is to avoid using 'hastctl role primary all', start providers one by one instead. -- Mikolaj Golub
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86wrjj5xfm.fsf>