From nobody Fri Sep 06 22:22:16 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 4X0rMG0hvMz5W6sT for ; Fri, 06 Sep 2024 22:22:34 +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 4X0rMF5Nhnz4LFp; Fri, 6 Sep 2024 22:22:33 +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=vw98N5dd917PA0j5PXb3yb2eT/MVw//UavmdR5lccNE=; b=LcfjEsGxhJ7OeJoZUKZTYACFkBVmLA3DC89qWxMg7jNFIaVeqj9gauxDP3h65UCekuXYL8EFeEy5g6Y+ZxFW94H3+LPseNgevFnsm9FXgLD3M80ZHHCLHBrF6M2qsbI3Gq0xmUGhIQzw8vopKWMiTEkXgzq6M3aTXZ9ZEHmpX+NVNitF2xIW8DJ1O0ODO3smJm2zwxe8ChhXTMzjh7kteL1HCNtg69f7dT4TnG67QvnfhtTwLAniqILdZ4 0svylL9+XPenb8X4YgimwVniA0gzthpsu/mNNVBi0sHMxYUCAzyYs/Bo7mfMnM/x7k0uw04YrZmGSFct626LjBx1FuRg== 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 22:22:30 +0000 Received: from smtpclient.apple ( [2001:420:c0c4:1001::9f]) by tristain.distal.com (OpenSMTPD) with ESMTPSA id 9cd54e1f (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Fri, 6 Sep 2024 18:22:28 -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 18:22:16 -0400 Cc: Wes Morgan , FreeBSD Filesystems Content-Transfer-Encoding: quoted-printable Message-Id: References: <5ED5CB56-2E2A-4D83-8CDA-6D6A0719ED19@distal.com> <6A20ABDA-9BEA-4526-94C1-5768AA564C13@distal.com> <0CF1E2D7-6C82-4A8B-82C3-A5BF1ED939CF@distal.com> <29003A7C-745D-4A06-8558-AE64310813EA@distal.com> <42346193-AD06-4D26-B0C6-4392953D21A3@gmail.com> <50B791D8-F0CC-431E-93B8-834D57AB3C14@gmail.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: 4X0rMF5Nhnz4LFp > On Sep 6, 2024, at 18:02, Alan Somers wrote: > Another user reports the same error message. In their case, it's an > inappropriate error message from /sbin/zpool. Can you try a "zpool > status -v" and "diskinfo -f /dev/da10"? That will show you if you > have the same problem. If your pool has a 512B block size but the new > disk is 4kn, then you cannot use it as a replacement. >=20 > https://github.com/openzfs/zfs/issues/14730 Yeah, I came across that in my searching. Although, I thought people=20 had found success adding =E2=80=9C-o ashift=3D9=E2=80=9D to the replace = command. I can confirm that this raidz1 is ashift=3D9, and the disks in it 512 byte sectorsize. The other two raidz=E2=80=99s are ashift=3D12. diskinfo shows 512 as sectorsize for one of the older disks (matching model to the removed da3), and 4096 sectorsize for the new disk. Is this totally impossible? I know I have replaced smaller disks with much larger ones in the past, though it=E2=80=99s been a few years and I don=E2=80=99t remember the details. Is there really no way to put a = 4k block disk in a set with 512 byte blocks? I thought they were still able to =E2=80=9Cact=E2=80=9D like 512-byte block disks? (512e) - Chris=