Date: Sat, 16 Feb 2019 19:48:28 +0100 From: Ireneusz Pluta <ipluta@wp.pl> To: Matthias Oestreicher <matthias@smormegpa.no>, freebsd-questions@freebsd.org Subject: Re: Sector size change with camcontrol Message-ID: <6a56b96e-7c4b-e108-7294-8be69e0f8ec6@wp.pl> In-Reply-To: <53922cb7f04e5399ee5f71dab24d9ee0c1536a10.camel@smormegpa.no> References: <b34979ac-d41c-413a-9ce8-c66b40d41512@wp.pl> <53922cb7f04e5399ee5f71dab24d9ee0c1536a10.camel@smormegpa.no>
next in thread | previous in thread | raw e-mail | index | archive | help
W dniu 2019-02-16 o 18:41, Matthias Oestreicher pisze: > As from the manual, your drive is physically a 4K drive already, even if it REPORTS to have a > sector size of 512 bytes. It's irrelevant what the drives reports in FreeBSD. Matthias, thank you for your extensive explanation. That's all clear. My only point in attempting to change (reported) sector size is to improve performance. Wouldn't 4k seen by the OS allow to have higher IOPS, as compared to 512? To make the view complete: the drives are going to run in a 24-bay backplane, as a zpool created as: zpool create data \ mirror /dev/label/da0 /dev/label/da1 \ mirror /dev/label/da2 /dev/label/da3 \ ... mirror /dev/label/da20 /dev/label/da21 \ spare /dev/label/da22 /dev/label/da23
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6a56b96e-7c4b-e108-7294-8be69e0f8ec6>