Date: Wed, 1 Oct 2014 15:44:32 +0300 From: George Kontostanos <gkontos.mail@gmail.com> To: Jordan Hubbard <jkh@mail.turbofuzz.com> Cc: freebsd-fs@freebsd.org, JF-Bogaerts <JF-Bogaerts@skynet.be> Subject: Re: HAST with broken HDD Message-ID: <CA%2BdUSyqNs6uPyKV1a=RVAHrr%2B-=nhOpi0-EgUb%2BVZ49vScDeNA@mail.gmail.com> In-Reply-To: <15E8A3A7-2CFA-43F0-B9DB-1B0DBAB5304C@mail.turbofuzz.com> References: <542BC135.1070906@Skynet.be> <542BDDB3.8080805@internetx.com> <CA%2BdUSypO8xTR3sh_KSL9c9FLxbGH%2BbTR9-gPdcCVd%2Bt0UgUF-g@mail.gmail.com> <15E8A3A7-2CFA-43F0-B9DB-1B0DBAB5304C@mail.turbofuzz.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 1, 2014 at 3:34 PM, Jordan Hubbard <jkh@mail.turbofuzz.com>
wrote:
>
> > On Oct 1, 2014, at 3:28 PM, George Kontostanos <gkontos.mail@gmail.com>
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BdUSyqNs6uPyKV1a=RVAHrr%2B-=nhOpi0-EgUb%2BVZ49vScDeNA>