Date: Fri, 6 Sep 2024 16:28:31 -0600 From: Alan Somers <asomers@freebsd.org> To: Chris Ross <cross+freebsd@distal.com> Cc: Wes Morgan <morganw@gmail.com>, FreeBSD Filesystems <freebsd-fs@freebsd.org> Subject: Re: Unable to replace drive in raidz1 Message-ID: <CAOtMX2iV7bG7E-uOOVsFVEzO7CDhRfHm12Y40EEQ25FYGxHFJA@mail.gmail.com> In-Reply-To: <E22575F4-8731-471A-A714-D391BD043FA8@distal.com> References: <5ED5CB56-2E2A-4D83-8CDA-6D6A0719ED19@distal.com> <AC67D073-D476-41F5-AC53-F671430BB493@distal.com> <CAOtMX2h52d0vtceuwcDk2dzkH-fZW32inhk-dfjLMJxetVXKYg@mail.gmail.com> <CB79EC2B-E793-4561-95E7-D1CEEEFC1D72@distal.com> <CAOtMX2i_zFYuOnEK_aVkpO_M8uJCvGYW%2BSzLn3OED4n5fKFoEA@mail.gmail.com> <6A20ABDA-9BEA-4526-94C1-5768AA564C13@distal.com> <CAOtMX2jfcd43sBpHraWA=5e_Ka=hMD654m-5=boguPPbYXE4yw@mail.gmail.com> <0CF1E2D7-6C82-4A8B-82C3-A5BF1ED939CF@distal.com> <CAOtMX2hRJvt9uhctKvXO4R2tUNq9zeCEx6NZmc7Vk7fH=HO8eA@mail.gmail.com> <29003A7C-745D-4A06-8558-AE64310813EA@distal.com> <42346193-AD06-4D26-B0C6-4392953D21A3@gmail.com> <E6C615C1-E9D2-4F0D-8DC2-710BAAF10954@distal.com> <E85B00B1-7205-486D-800C-E6837780E819@gmail.com> <E93A9CA8-6705-4C26-9F33-B620A365F4BD@distal.com> <50B791D8-F0CC-431E-93B8-834D57AB3C14@gmail.com> <E50559CA-CC3D-45AE-82D7-172270BF4851@distal.com> <CAOtMX2ihPqe9w%2BhbZ=GqOcmmN%2B8y9-%2Bqyew9CfZV9ajpGHZmXA@mail.gmail.com> <E22575F4-8731-471A-A714-D391BD043FA8@distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 6, 2024 at 4:22=E2=80=AFPM Chris Ross <cross+freebsd@distal.com= > wrote: > > > > > On Sep 6, 2024, at 18:02, Alan Somers <asomers@freebsd.org> 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. > > > > https://github.com/openzfs/zfs/issues/14730 > > Yeah, I came across that in my searching. Although, I thought people > had found success adding =E2=80=9C-o ashift=3D9=E2=80=9D to the replace c= ommand. > 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 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. -Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2iV7bG7E-uOOVsFVEzO7CDhRfHm12Y40EEQ25FYGxHFJA>