From owner-freebsd-fs@FreeBSD.ORG Wed Oct 1 12:44:34 2014 Return-Path: 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 6E5EF6C7 for ; Wed, 1 Oct 2014 12:44:34 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (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 06BFEEFF for ; Wed, 1 Oct 2014 12:44:33 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id cc10so385948wib.0 for ; Wed, 01 Oct 2014 05:44:32 -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=9P8ORLK9mEaO68RMelVaiO/+BmOrVuOLaQV5sJJV23o=; b=D53es3vAkASWscHCcVeACEvNAvimpr0LC22wVxMbDbasaTDYNWLwhEisBRa4o/clGW OeWa9+lTErcjHExl75+dpWQPNZTGnIMwHTVkedQfACuIh3M6VsnfAeoiLmLYcI2WWCuE gvSXWvt47BHAr+I0POokaosse8IBTUcuGNGEEQLtOrfKtragfdYx7ZPOYCgBhc8icAO6 TxiwLWkBNhpVqy38qyHVvJVERkFRVQdqdqslU3IGRFCwqRIh5KOFSsanzOPRsddRxe6Q NMwCL7J+B31SaEGq3/aeOKAWOCxZbgJtNzHODJtMhiYvB9Hw0bY3NCGfWhRCWvRaYf6l Qx7Q== MIME-Version: 1.0 X-Received: by 10.180.97.199 with SMTP id ec7mr14152654wib.29.1412167472301; Wed, 01 Oct 2014 05:44:32 -0700 (PDT) Received: by 10.27.137.130 with HTTP; Wed, 1 Oct 2014 05:44:32 -0700 (PDT) In-Reply-To: <15E8A3A7-2CFA-43F0-B9DB-1B0DBAB5304C@mail.turbofuzz.com> References: <542BC135.1070906@Skynet.be> <542BDDB3.8080805@internetx.com> <15E8A3A7-2CFA-43F0-B9DB-1B0DBAB5304C@mail.turbofuzz.com> Date: Wed, 1 Oct 2014 15:44:32 +0300 Message-ID: Subject: Re: HAST with broken HDD From: George Kontostanos To: Jordan Hubbard 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 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2014 12:44:34 -0000 On Wed, Oct 1, 2014 at 3:34 PM, Jordan Hubbard wrote: > > > On Oct 1, 2014, at 3:28 PM, George Kontostanos > wrote: > > Are you saying that the pool will appear to be optimal even with a bad > drive? > > Yes. HAST means that ZFS won=E2=80=99t *see* a bad drive. It will just = continue > to see =E2=80=9Ca drive=E2=80=9D even though one half of the HAST pair ha= s died. > > - Jordan > > > Given the fact that the pool is available only on the active server, I find it interesting that any write operation to that pool will not produce a checksum error. I am going to certainly try and create the problem on a test environment that I currently have with ZFS and HAST root@hast1:~ # zpool status pool: tank state: ONLINE scan: scrub repaired 0 in 0h1m with 0 errors on Tue Sep 30 21:55:16 2014 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 hast/disk1 ONLINE 0 0 0 hast/disk2 ONLINE 0 0 0 errors: No known data errors