From nobody Fri Sep 06 18:06:32 2024 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4X0kh75YT9z5VPJX for ; Fri, 06 Sep 2024 18:06:47 +0000 (UTC) (envelope-from cross+freebsd@relay.distal.com) Received: from relay.wiredblade.com (relay.wiredblade.com [168.235.95.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X0kh731Wdz4KYQ; Fri, 6 Sep 2024 18:06:47 +0000 (UTC) (envelope-from cross+freebsd@relay.distal.com) Authentication-Results: mx1.freebsd.org; none dkim-signature: v=1; a=rsa-sha256; d=relay.distal.com; s=mail; c=relaxed/relaxed; q=dns/txt; h=From:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References; bh=8ROrnENf/y2tprcw3YaIAWUhaj71MeY73/qJy/AcM2Q=; b=NQ6U6zKYo5KQVVwFfGEIXII+Rc/v/t4btgRv6IIlGBQ/GiMQoXrdshdRGCsCt6CvhyqfT+U5i6leb+qjTqxwK3Sk4wsLc7SqHMJoxtSGdujo8N9PsFcX+aDtRJp0nV+FCUoyVDsNIJ00mjLMVDua7WU/2IK9OHGa/TQOINzlDk4LXzoBrzfKV8+rhINqLvVoO7ycn8e72DzyaaUpEgQo0nIheu6biZpjQuPsNZoZIdltfBG0nmvMZjfat1 jecFmWmGFWpSoNIEgGpKxon/WTAq8RBiBXm9J6WZMAD4nwyZfVYzsfm46StQzqQgutv+Jl/SlY6eY+EP7nsWeMmlZuWQ== Received: from mail.distal.com (pool-108-51-233-124.washdc.fios.verizon.net [108.51.233.124]) by relay.wiredblade.com with ESMTPSA (version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256) ; Fri, 6 Sep 2024 18:06:45 +0000 Received: from smtpclient.apple ( [2001:420:c0c4:1001::9f]) by tristain.distal.com (OpenSMTPD) with ESMTPSA id 9822b920 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Fri, 6 Sep 2024 14:06:43 -0400 (EDT) Content-Type: text/plain; charset=utf-8 List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\)) Subject: Re: Unable to replace drive in raidz1 From: Chris Ross In-Reply-To: Date: Fri, 6 Sep 2024 14:06:32 -0400 Cc: mike tancsa , FreeBSD Filesystems Content-Transfer-Encoding: quoted-printable Message-Id: <0CF1E2D7-6C82-4A8B-82C3-A5BF1ED939CF@distal.com> References: <5ED5CB56-2E2A-4D83-8CDA-6D6A0719ED19@distal.com> <6A20ABDA-9BEA-4526-94C1-5768AA564C13@distal.com> To: Alan Somers X-Mailer: Apple Mail (2.3776.700.51) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[freebsd]; ASN(0.00)[asn:3842, ipnet:168.235.92.0/22, country:US] X-Rspamd-Queue-Id: 4X0kh731Wdz4KYQ > On Sep 6, 2024, at 13:59, Alan Somers wrote: >=20 > On Fri, Sep 6, 2024 at 11:50=E2=80=AFAM Chris Ross = wrote: >> % sudo zpool replace tank da3 da10 >> cannot replace da3 with da10: already in replacing/spare config; wait = for completion or use 'zpool detach' >>=20 >>=20 >=20 > If there is no label on da10, and "zpool status" doesn't show any > spares, then I don't know what the problem is. It's possible that > /sbin/zpool is printing an incorrect error message; it's fairly > notorious for that. You could try to debug it. Other wild guesses > include: > * maybe da3 is the disk with the out-of-date label. You could try > physically removing it before doing "zpool replace" Well, there is a problem there. /dev/da3, right now, is one of the disks in zraid1-1, the second set. It=E2=80=99s working there, = listed as diskid/??? How can I map the diskid=E2=80=99s listed to the underlying device? either by serial number or da#=E2=80=A6 > * Since exported pools can't have active spares, you could try > exporting the pool and then reimporting it. Okay. Lukcily this is _not_ a root on ZFS system, so that should be doable. Hopefully there aren=E2=80=99t significant risks there? Can I tell ZFS to reconsider the labels in the first zraid1? since it=E2=80=99s still reporting da3 as missing/failed, and that = kernel dev is not what it thinks that is=E2=80=A6 - Chris