Date: Thu, 13 Sep 2018 17:13:47 -0700 From: Matthew Pounsett <matt@conundrum.com> To: freebsd-questions@freebsd.org Subject: Re: Issues replacing a failed disk in a zfs pool Message-ID: <CAAiTEH-97d3OMtPxLpGfCTjJwYfKZdXQJkP4NgDuN20K611U%2BQ@mail.gmail.com> In-Reply-To: <CAAiTEH9xxN145N33MjQBYsxe1=FgYrkGL2YiCK2V8V_MdoB2SA@mail.gmail.com> References: <CAAiTEH9xxN145N33MjQBYsxe1=FgYrkGL2YiCK2V8V_MdoB2SA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13 September 2018 at 16:28, Matthew Pounsett <matt@conundrum.com> wrote:
> I just tried bringing the disk back online, and zfs now says it's being
> resilvered. I assume it's going to take longer to complete than I'm going
> to be here, so the replacement will now probably have to wait for my next
> visit.
>
> That went very quickly. That 'spare-4' replacement line now looks like
this:
spare-4 ONLINE 0 0 0
diskid/DISK-PK2331PAG704VT ONLINE 0 0 0 block size:
512B configured, 4096B native
da23 ONLINE 0 0 0 block size:
512B configured, 4096B native
I'm not sure what I'm meant to do here. da23 is a spare that was brought
in to replace DISK-PK2331PAG704VT when it failed, but they now seem to be
joined at the hip.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAAiTEH-97d3OMtPxLpGfCTjJwYfKZdXQJkP4NgDuN20K611U%2BQ>