On Tue, 9 Feb 2021 at 19:13, David Brownlee <a...@absd.org> wrote: > > Has the native disk block size reported via sata devices changed > recently in netbsd-9?
It has! Test booted a netbsd-9.0_RELEASE and netbsd-9.1_RELEASE kernels on a sample server (otherwise running netbsd-9.1_STABLE). To confirm - this is entirely a kernel difference, no change in userland in the below tests. netbsd-9.0: pool: onyx0 state: ONLINE scan: scrub repaired 0 in 4h45m with 0 errors on Tue Jan 21 00:50:23 2020 config: NAME STATE READ WRITE CKSUM onyx0 ONLINE 0 0 0 wd1 ONLINE 0 0 0 netbsd-9.1: pool: onyx0 state: ONLINE 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. scan: scrub repaired 0 in 4h45m with 0 errors on Tue Jan 21 00:50:23 2020 config: NAME STATE READ WRITE CKSUM onyx0 ONLINE 0 0 0 wd1 ONLINE 0 0 0 block size: 512B configured, 4096B native Of course, now that I _have_ this information, I'm somewhat nonplussed. If I'm ever in a position to conventinely rebuild the ZFS pools on the two affected servers I will, but otherwise I suspect I park this (reminder - I have another server originally built with a later kernel version which does not show this issue, as the pool on wd disks uses 4096 byte block size) David