From nobody Fri Sep 06 22:53:26 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 4X0s3C12Hpz5W9rW for ; Fri, 06 Sep 2024 22:53:43 +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 4X0s3B4T6Gz4RN1; Fri, 6 Sep 2024 22:53:42 +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=A03Lf8iBCQGvBUVLskf/eggG6HM0l6C+Q1kJtQFCBL4=; b=pLmP9YPoaDRbyNE9lpkrnD2cJ3ebD9BmYOa4641cz1RNl4aeN5cEQvLtfQj/TZPebESlurpjKnKRxb08FS1rqHTJq92EVpvQ7yL4DbUxJFMRCTGipT5ht2XiSCmoGpPICFyMjc3RRDyJd+IVr+Bb23v6Kn239YcuK8kAEUgwttxq0IMdM/IYceaqRyVdslOyBhj04oiCDrZ+sJTcQe7gUOpH9nRmwFQS+E2Q5CCSA1qHHo0LmLlfx3XP61 pmrYJ6ZfSnNGWgsrTDWk9qgJS3lBaqMXKDZ86wGeCjP0/JUy1qw8HPMrqBFMB1lhMzDIsx6vNdSBxMuFUeG4DiTdDZVQ== 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:53:39 +0000 Received: from smtpclient.apple ( [2001:420:c0c4:1001::9f]) by tristain.distal.com (OpenSMTPD) with ESMTPSA id e351909a (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Fri, 6 Sep 2024 18:53:37 -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:53:26 -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: 4X0s3B4T6Gz4RN1 > 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. Hmm. Okay. Though there are 6TB disks in the other array that are quite old, I=E2=80=99m pretty sure could work in 512e mode, but diskinfo = shows a 4096 sectorsize for those too. Oh well, I could be wrong about how they work. I can definately find another drive, likely even of the correct size. But, that breaks my plan to increase the size of the pool by replacing disks. Am I correct that FreeBSD offers no way to remove raidz vdev=E2=80=99s from a pool? If it could I could try to = construct some sort of new pool a piece at a time. But if it does not, then there is nothing I can do I assume. :-/ 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. :-) - Chris