From owner-freebsd-fs@FreeBSD.ORG  Wed Oct  1 12:49:25 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 7AEAAA7B
 for <freebsd-fs@freebsd.org>; Wed,  1 Oct 2014 12:49:25 +0000 (UTC)
Received: from mx1.internetx.com (mx1.internetx.com [62.116.129.39])
 by mx1.freebsd.org (Postfix) with ESMTP id 34E2AF6E
 for <freebsd-fs@freebsd.org>; Wed,  1 Oct 2014 12:49:24 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by mx1.internetx.com (Postfix) with ESMTP id 38A824C4CDB2;
 Wed,  1 Oct 2014 14:49:23 +0200 (CEST)
X-Virus-Scanned: InterNetX GmbH amavisd-new at ix-mailer.internetx.de
Received: from mx1.internetx.com ([62.116.129.39])
 by localhost (ix-mailer.internetx.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id sSa2zOi-9eVq; Wed,  1 Oct 2014 14:49:20 +0200 (CEST)
Received: from [192.168.100.26] (pizza.internetx.de [62.116.129.3])
 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.internetx.com (Postfix) with ESMTPSA id B1A904C4CD22;
 Wed,  1 Oct 2014 14:49:20 +0200 (CEST)
Message-ID: <542BF853.3040604@internetx.com>
Date: Wed, 01 Oct 2014 14:49:23 +0200
From: InterNetX - Juergen Gotteswinter <jg@internetx.com>
Reply-To: jg@internetx.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: George Kontostanos <gkontos.mail@gmail.com>
Subject: Re: HAST with broken HDD
References: <542BC135.1070906@Skynet.be>	<542BDDB3.8080805@internetx.com>
 <CA+dUSypO8xTR3sh_KSL9c9FLxbGH+bTR9-gPdcCVd+t0UgUF-g@mail.gmail.com>
In-Reply-To: <CA+dUSypO8xTR3sh_KSL9c9FLxbGH+bTR9-gPdcCVd+t0UgUF-g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
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:49:25 -0000

Am 01.10.2014 um 14:28 schrieb George Kontostanos:
> 
> On Wed, Oct 1, 2014 at 1:55 PM, InterNetX - Juergen Gotteswinter
> <jg@internetx.com <mailto: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çois 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?  
> 
> 

https://forums.freebsd.org/viewtopic.php?&t=24786