From nobody Fri Sep 6 18:10:22 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 4X0kmX68Wdz5VPJy for ; Fri, 06 Sep 2024 18:10:36 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f180.google.com (mail-oi1-f180.google.com [209.85.167.180]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X0kmW4pKrz4L9c for ; Fri, 6 Sep 2024 18:10:35 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none); spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.167.180 as permitted sender) smtp.mailfrom=asomers@gmail.com Received: by mail-oi1-f180.google.com with SMTP id 5614622812f47-3df0e0e5577so1387987b6e.0 for ; Fri, 06 Sep 2024 11:10:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725646234; x=1726251034; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=5E9VocnPsFQXrzH2F7ELwusDNceTpQj1VKUKD7VWj1A=; b=lU4jrIk1lrTA+VaFAOkM8xczlJ/MFw3sysPmvGPLquXWkUCG5KJ7L4wpuqZZ0ThfmO /Y3ELhRbCnTWFySC1Ygk9Qe1iOos4UFAVjrwgW70UUXd3wxaHKsEKFaU4/Kctx2TdzUl wbDJi3+L43upjpIMymoHubfxcT3KtEu/AUFgCApzlQHyXijsy4+UlpAsTVTJWZWQ15+l nDt5DZmq+YbTrkd2aP4XcVQWbrUgH+3hYaX+TESgDdN1P/GBzhND4eqVjccMluyJSeOy th1F1KVdMMmJW1fNKqsY9LFJzO/UMLeehZrGiciBLqnPWjpXFLK+4VP63RXyaa6UmIzS GZKw== X-Forwarded-Encrypted: i=1; AJvYcCWbWLLXe/0BGVpMb7r1q6crTJKcjg0q5AqcBdT8eLqTpeQ7JKYh+vyjJhhjz9+QyeUMN9AIywR3C2J3@freebsd.org X-Gm-Message-State: AOJu0Yx05Qx8IkG1nywSqxjA/6ZK97M2yVOT+3b8l/a96HQT8LbcCc6o lW2J0UScDfrf8H/CbHMuXDE1eu6Xp1pSZ7MFL4//exmG+DI25G8EXEzxqcTJvjSzc6pVSXj05mC VocPRoyzO4J4yaXnMF7xLtayVqth+evOK X-Google-Smtp-Source: AGHT+IHMO7htfHnBW+j3BD1A5+kZTmlU0N2aBfqcrqPLQvPB1FxYNseyoh/xqT2q6sJYic8FJ3xyb4D4fN6tXhp9Kic= X-Received: by 2002:a05:6808:1709:b0:3df:144f:9ef9 with SMTP id 5614622812f47-3e02a02d73cmr3922999b6e.41.1725646234367; Fri, 06 Sep 2024 11:10:34 -0700 (PDT) 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 References: <5ED5CB56-2E2A-4D83-8CDA-6D6A0719ED19@distal.com> <6A20ABDA-9BEA-4526-94C1-5768AA564C13@distal.com> <0CF1E2D7-6C82-4A8B-82C3-A5BF1ED939CF@distal.com> In-Reply-To: <0CF1E2D7-6C82-4A8B-82C3-A5BF1ED939CF@distal.com> From: Alan Somers Date: Fri, 6 Sep 2024 12:10:22 -0600 Message-ID: Subject: Re: Unable to replace drive in raidz1 To: Chris Ross Cc: mike tancsa , FreeBSD Filesystems Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.38 / 15.00]; NEURAL_HAM_LONG(-1.00)[-0.996]; NEURAL_HAM_MEDIUM(-0.75)[-0.753]; NEURAL_HAM_SHORT(-0.73)[-0.735]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; RCPT_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; FREEFALL_USER(0.00)[asomers]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; TAGGED_RCPT(0.00)[freebsd]; R_DKIM_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.167.180:from]; RCVD_IN_DNSWL_NONE(0.00)[209.85.167.180:from] X-Rspamd-Queue-Id: 4X0kmW4pKrz4L9c On Fri, Sep 6, 2024 at 12:06=E2=80=AFPM Chris Ross wrote: > > > > > On Sep 6, 2024, at 13:59, Alan Somers wrote: > > > > 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' > >> > >> > > > > 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, liste= d > 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 The gpart command should do it, but I don't recommend that. Instead, see below... > > > * 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 Ahh, this means that there are two different vdevs that can be described by "da3". You can still refer to them unambiguously by guid though. Do "zpool status -g" to find the guid of the disk that you want to replace, and then do "zpool replace /dev/da10"