From nobody Fri Sep 06 17:50:31 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 4X0kKg69Htz5VMVR for ; Fri, 06 Sep 2024 17:50: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 4X0kKg1qnSz4F3w; Fri, 6 Sep 2024 17:50: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=qJURHgQq3Bnoivbpiymn0dmDSeiboh8hmAcGsBkFrD0=; b=YlrFeblUQhHSziLzWtLxMIqCICe+lHYSAZPX6K5qTOxlyKkRIbyBL+tKiqI7xQI7+9YeULphzCaNc/3+m4sOifY9e5gvh6fGZCBw28mSigWBHA277Iwr9aflHEQzShY8TwjKumaXuuE4Oa9DV5XElfxw/CqPgUfOAOIcTf7eQsOV/4O0uLOvJuWUqrNbthCvVkMX1prtZzwc1ZeD/pyfkssmPWTH0c7DqyXuG3jRboh/9gE3hidA8QiDUb +FujLqHx53yTh0TTURm0o0piVA70HIpt8dsHtG/rkr8A7QyywWU+CC6PbgZPFn1RXbFLRBLKsyvA94C1QsVtNvSpZ2ZQ== 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 17:50:45 +0000 Received: from smtpclient.apple ( [2001:420:c0c4:1001::9f]) by tristain.distal.com (OpenSMTPD) with ESMTPSA id 325d6f1e (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Fri, 6 Sep 2024 13:50: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 13:50:31 -0400 Cc: mike tancsa , FreeBSD Filesystems Content-Transfer-Encoding: quoted-printable Message-Id: <6A20ABDA-9BEA-4526-94C1-5768AA564C13@distal.com> References: <5ED5CB56-2E2A-4D83-8CDA-6D6A0719ED19@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: 4X0kKg1qnSz4F3w > On Sep 6, 2024, at 13:02, Alan Somers wrote: >=20 > This looks like you got into a split-brain situation where the disks > have inconsistent labels. Most disks think that da10 is not a member > of the pool, but da10 thinks that it is. Perhaps you added it as a > spare, then physically removed it, and then did a "zpool remove" to > remove the spare from the configuration? I did configure it as a spare, and remove it as a spare, but I=20 haven=E2=80=99t moved any disks physically since the once when I=20 switched it in. And this problem started before I ever tried adding da10 into the pool as a spare. > If you're very very very > sure that there is no data on da10 that you care about, you can do > "zpool labelclear -f /dev/da10=E2=80=9D I am sure, and I didn=E2=80=99t even need the -f. But, no change. % sudo zpool labelclear /dev/da10 Password: % sudo zdb -l /dev/da10 failed to unpack label 0 failed to unpack label 1 failed to unpack label 2 failed to unpack label 3 % sudo zpool replace tank da3 da10 cannot replace da3 with da10: already in replacing/spare config; wait = for completion or use 'zpool detach' :-( - Chris=