From owner-freebsd-fs@FreeBSD.ORG  Wed Oct  1 12:28:35 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D2F0EE1D
 for <freebsd-fs@freebsd.org>; Wed,  1 Oct 2014 12:28:35 +0000 (UTC)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com
 [IPv6:2a00:1450:400c:c05::231])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 6EDD4CE7
 for <freebsd-fs@freebsd.org>; Wed,  1 Oct 2014 12:28:35 +0000 (UTC)
Received: by mail-wi0-f177.google.com with SMTP id ho1so373864wib.16
 for <freebsd-fs@freebsd.org>; Wed, 01 Oct 2014 05:28:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=7kFE+OdD1nynd/1qaHraaRtq1VLFKNCczJa7tjATB6E=;
 b=r21VonK6QOhFWCfi3zsgNTpHl4H+iBfNNPnyuWkwO83BSnheaGFcRFy5TsAyIa3o1R
 9CvJ0X5Wtd0Klv9w5qj1CGOaWcl9s8C7ynRW8zW4iDNltUUCJICLDOIVWTsg8IyJpMyw
 GNesuewSZ4JgfM44B/1W5+/K0W15CuMA40qKUNM2Bnsce9op07468xa/X74k/N7NqXo8
 NQSssvLi9RpJt7QDPqEzWTjhSUto1NfZSfbr8lkkYyPK8alniJ8O3Kd1fqsgo99ZGZLH
 9BbexyKX2uNp47XefBZuatU+sDRNDgKwldQKReR+yzOh1BNlMtkVAn2I7HZcXxSC1qQp
 qIbA==
MIME-Version: 1.0
X-Received: by 10.194.189.82 with SMTP id gg18mr2573323wjc.2.1412166513730;
 Wed, 01 Oct 2014 05:28:33 -0700 (PDT)
Received: by 10.27.137.130 with HTTP; Wed, 1 Oct 2014 05:28:33 -0700 (PDT)
In-Reply-To: <542BDDB3.8080805@internetx.com>
References: <542BC135.1070906@Skynet.be>
	<542BDDB3.8080805@internetx.com>
Date: Wed, 1 Oct 2014 15:28:33 +0300
Message-ID: <CA+dUSypO8xTR3sh_KSL9c9FLxbGH+bTR9-gPdcCVd+t0UgUF-g@mail.gmail.com>
Subject: Re: HAST with broken HDD
From: George Kontostanos <gkontos.mail@gmail.com>
To: jg@internetx.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: freebsd-fs@freebsd.org, JF-Bogaerts <JF-Bogaerts@skynet.be>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Oct 2014 12:28:36 -0000

On Wed, Oct 1, 2014 at 1:55 PM, InterNetX - Juergen Gotteswinter <
jg@internetx.com> wrote:

> Am 01.10.2014 um 10:54 schrieb JF-Bogaerts:
> >    Hello,
> >    I'm preparing a HA NAS solution using HAST.
> >    I'm wondering what will happen if one of disks of the primary node
> will
> >    fail or become erratic.
> >
> >    Thx,
> >    Jean-Fran=C3=A7ois Bogaerts
>
> nothing. if you are using zfs on top of hast zfs wont even take notice
> about the disk failure.
>
> as long as the write operation was sucessfull on one of the 2 nodes,
> hast doesnt notify the ontop layers about io errors.
>
> interesting concept, took me some time to deal with this.
>
>
> Are you saying that the pool will appear to be optimal even with a bad
drive?