Date: Sat, 23 Sep 2023 20:12:35 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: Frank Behrens <frank@harz2023.behrens.de> Cc: freebsd-stable@freebsd.org Subject: Re: nvd->nda switch and blocksize changes for ZFS Message-ID: <D20AFDEE-45F4-40AF-A401-023E69A5C8A6@FreeBSD.org> In-Reply-To: <1b6190d1-1d42-6c99-bef6-c6b77edd386a@harz2023.behrens.de> References: <1b6190d1-1d42-6c99-bef6-c6b77edd386a@harz2023.behrens.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_4B998D1C-DD4B-409F-AA24-9AB80B5A4A91 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 23 Sep 2023, at 18:31, Frank Behrens <frank@harz2023.behrens.de> = wrote: >=20 > I created a zpool with a FreeBSD-14.0-CURRENT on February. With = 15.0-CURRENT/14.0-STABLE from now I get the message: >=20 > status: One or more devices are configured to use a non-native block = size. > Expect reduced performance. > action: Replace affected devices with devices that support the > configured block size, or migrate data to a properly = configured > pool. > NAME STATE READ WRITE CKSUM > zsys ONLINE 0 0 0 > raidz1-0 ONLINE 0 0 0 > nda0p4 ONLINE 0 0 0 block size: 4096B = configured, 16384B native > nda1p4 ONLINE 0 0 0 block size: 4096B = configured, 16384B native > nda2p4 ONLINE 0 0 0 block size: 4096B = configured, 16384B native >=20 > I use: > nda0: <Samsung SSD 980 1TB ..> > nda0: nvme version 1.4 > nda0: 953869MB (1953525168 512 byte sectors) >=20 > I cannot imagine, that the native blocksize changed. Do I really = expect a reduced performance? > Is it advisable to switch back to nvd? It could be due to a bug in nda so it reports the native block size = incorrectly, in which case you would not need to do anything but ignore = the message. However, if the native block size is really 16kiB, you will = get write amplification effects, which could needlessly shorten the life = of your SSD. I would try running e.g. smartmontools's smartctl, which can sometimes = tell you what the real block size is. Although as far as I know, it = retrieves this information from some internal database. You could also = try to look up the information in the SSD vendor's data sheet, or ask = the vendor directly? -Dimitry --Apple-Mail=_4B998D1C-DD4B-409F-AA24-9AB80B5A4A91 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCZQ8qkwAKCRCwXqMKLiCW o/GQAJwK/AafYZZR8OGo3ktZWjXiNghqZACgjnKr4tH/FYhdNd3tkvXMDsK8aZc= =Wf4G -----END PGP SIGNATURE----- --Apple-Mail=_4B998D1C-DD4B-409F-AA24-9AB80B5A4A91--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D20AFDEE-45F4-40AF-A401-023E69A5C8A6>