From nobody Mon Sep 09 14:56:08 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 4X2VKC3hWhz5Wc38 for ; Mon, 09 Sep 2024 14:56:31 +0000 (UTC) (envelope-from cross+freebsd@relay.distal.com) Received: from relay.wiredblade.com (relay.wiredblade.com [168.235.105.136]) (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 4X2VKB0tsCz4f6f; Mon, 9 Sep 2024 14:56:29 +0000 (UTC) (envelope-from cross+freebsd@relay.distal.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=relay.distal.com header.s=mail header.b=XRGa2QLu; dmarc=none; spf=pass (mx1.freebsd.org: domain of cross+freebsd@relay.distal.com designates 168.235.105.136 as permitted sender) smtp.mailfrom=cross+freebsd@relay.distal.com 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=tZzrFfS16cp1RGLFYTVIrUpXpMru+m+BfQ+qyEp2muE=; b=XRGa2QLuucLVU+SvI905iTlLL2gTz6nCHMSXvoqRQio82Jwtfq3MBZ09wzIbO+fO9QxqaT6oOpuVTW25+rQs5vVdhHc+i5Yz3W7owYvML0uEJ8hrO/tN82vr7UMHQmvWrrn1CESR8JS/9dl4Dvdr4ChWhmBBKbAgpnwkedU3r40UDOF5V5nI78EqKdm46CoGagYQA5+dEyBX986ogtdIi/FUYt0fFrN8EKetiUBCr7HKnQ4oNBMGWiyK+f /UZVu84lFER/Mx+AOQcQgubDthk1dirrCeE8GTy5+lz6eWohkyTl4B2l94ImHcR0gnCUMiquaoN4vRPhlsoCBt7Jnlkw== 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) ; Mon, 9 Sep 2024 14:56:21 +0000 Received: from smtpclient.apple ( [2001:420:c0c4:1001::9f]) by tristain.distal.com (OpenSMTPD) with ESMTPSA id 70f15d4a (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Mon, 9 Sep 2024 10:56:19 -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: Mon, 9 Sep 2024 10:56:08 -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-Spamd-Result: default: False [-3.20 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[cross@distal.com,cross@relay.distal.com]; R_SPF_ALLOW(-0.20)[+a:relay.dynu.com]; R_DKIM_ALLOW(-0.20)[relay.distal.com:s=mail]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[relay.distal.com:+]; FROM_HAS_DN(0.00)[]; TAGGED_FROM(0.00)[freebsd]; TO_DN_ALL(0.00)[]; FREEMAIL_CC(0.00)[gmail.com,freebsd.org]; DMARC_NA(0.00)[distal.com]; RCPT_COUNT_THREE(0.00)[3]; ASN(0.00)[asn:3842, ipnet:168.235.104.0/22, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_NEQ_ENVFROM(0.00)[cross@distal.com,cross@relay.distal.com]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; APPLE_MAILER_COMMON(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4X2VKB0tsCz4f6f > On Sep 6, 2024, at 18:53, Chris Ross wrote: >> On Sep 6, 2024, at 18:28, Alan Somers wrote: >>=20 >> If it's a 4kn disk, then what you ask for is impossible. If it's >> 512e, then it should've already worked. With diskinfo, a 512e disk >> will have 512 sectorsize and 4096 stripesize. A 4kn disk will show >> 4096 sectorsize. If you cannot obtain a 512n or 512e disk, then I'm >> afraid that you'll have to recreate your whole pool. >=20 > Happy to hear other thoughts. I could move all of the data to > another system and rebuild it with a new vdev, but I=E2=80=99m not = sure > if I care to grow the FS enough to do that. :-) Okay, final question. If I destroy and rebuild the pool, and have a = RAIDz with 512-byte sector drives, can I replace those with larger 4k sector drives as long as I have created the vdev with =E2=80=9Cashift=3D12=E2=80=9D= ? You said =E2=80=9Cif your pool has a 512B block size=E2=80=9D. Does = that mean the ashift value, or is there something else that I=E2=80=99ll need to be mindful = of if I want to be able to upgrade to 4k disks? - Chris