Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Sep 2024 09:27:07 -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:  <CAOtMX2ikKpeLNK8h6TEUDWC_k8aYJ2XY=CFuUEaTA-KnfQT4ew@mail.gmail.com>
In-Reply-To: <AB480336-20A1-4861-808E-C39C1DF906B9@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> <CAOtMX2iV7bG7E-uOOVsFVEzO7CDhRfHm12Y40EEQ25FYGxHFJA@mail.gmail.com> <DDC050E5-2F19-4162-9B84-91C6787453B7@distal.com> <AB480336-20A1-4861-808E-C39C1DF906B9@distal.com>

index | next in thread | previous in thread | raw e-mail

On Mon, Sep 9, 2024 at 8:56 AM Chris Ross <cross+freebsd@distal.com> wrote:
>
>
>
> > On Sep 6, 2024, at 18:53, Chris Ross <cross+freebsd@distal.com> wrote:
> >> On Sep 6, 2024, at 18:28, Alan Somers <asomers@freebsd.org> wrote:
> >>
> >> 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.
> >
> > Happy to hear other thoughts.  I could move all of the data to
> > another system and rebuild it with a new vdev, but I’m 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 “ashift=12”?

Absolutely.  Just set vfs.zfs.min_auto_ashift=12 before you create the pool.

>
> You said “if your pool has a 512B block size”.  Does that mean the ashift
> value, or is there something else that I’ll need to be mindful of if
> I want to be able to upgrade to 4k disks?

Correct.  That means the ashift value.


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2ikKpeLNK8h6TEUDWC_k8aYJ2XY=CFuUEaTA-KnfQT4ew>