Date: Thu, 31 Aug 2017 15:18:01 +0100 From: Frank Leonhardt <frank2@fjl.co.uk> To: freebsd-questions@freebsd.org Subject: Re: help creating new gmirror > 2TB Message-ID: <59A81A99.3040000@fjl.co.uk> In-Reply-To: <59A7683F.5070102@gmail.com> References: <CAFsnNZLeuLYEJVozsoSvDtvgfMf4UueJhm37waOQ5_kyxs-rhg@mail.gmail.com> <26f5e88e-1ea7-6332-ca5e-f055cfbdd280@fjl.co.uk> <CAFsnNZ%2ByU-S1QBVJDrapy_N1mi3kUrHSbcbzNuDgTUceXwXPyA@mail.gmail.com> <59A7683F.5070102@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 31/08/2017 02:37, JD wrote: > I thought that hdparm could work with the firmware to set the sector > size. > Not sure on this because hdparm has gone through a lot of modifications > over the years. > In the good old days, a sector was a sector! Fixed in to the disk by drilling a hole and shining a light through it as it spun past a sensor. IDE (aka S/ATA drives lie a LOT about what they're really doing. If you want them to pretend their sectors are 512b they will. But on the hardware they're fixed at 4K, so they read 4K in and throw away 3.5K. It gets bad if your OS is reading one sector at a time and the drive isn't caching it; and as the FS block size is unlikely to be 512b it gets fraught quite quickly. As you need an inter-sector gap and each sector has an ECC overhead that's not proportional to it's length, having larger physical sectors also means more of the disk is used for data and less for padding and overhead. Regards, Frank.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?59A81A99.3040000>