Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 22 Apr 2024 17:18:46 +0200
From:      =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org>
To:        mike tancsa <mike@sentex.net>
Cc:        FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject:   Re: block size: 512B configured, 4096B native all of a sudden
Message-ID:  <86bk618lyh.fsf@ltc.des.dev>
In-Reply-To: <9a593ca1-4975-438a-afec-d8dd5199dbcf@sentex.net> (mike tancsa's message of "Mon, 22 Apr 2024 10:52:19 -0400")
References:  <9a593ca1-4975-438a-afec-d8dd5199dbcf@sentex.net>

next in thread | previous in thread | raw e-mail | index | archive | help
mike tancsa <mike@sentex.net> writes:
> I upgraded a RELENG_13 box from last March to one today to bring in
> some of the zfs bug fixes.  But now I have this warning on a pool that
> was not there before.  But the special devices (two 2TB samsungs) are
> 512 according to smartctl?  Any idea why this warning popped up on the
> pool all of a sudden?  the disks and pool have been the same for a
> year or so.

what does `sysctl vfs.zfs.vdev.min_auto_ashift` say?

> Sector Size:      512 bytes logical/physical

The SSD is doing read-copy-update behind the scenes to support a
512-byte sector size for compatibility reasons, the real sector size is
unlikely to be less than 4 kB and may actually be significantly larger.

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86bk618lyh.fsf>