HAST with broken HDD

George Kontostanos gkontos.mail at gmail.com
Wed Oct 1 12:44:34 UTC 2014


On Wed, Oct 1, 2014 at 3:34 PM, Jordan Hubbard <jkh at mail.turbofuzz.com>
wrote:

>
> > On Oct 1, 2014, at 3:28 PM, George Kontostanos <gkontos.mail at 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’t *see* a bad drive.  It will just continue
> to see “a drive” even though one half of the HAST pair has 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 at 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


More information about the freebsd-fs mailing list