Status of support for 4KB disk sectors

Jeremy Chadwick freebsd at jdc.parodius.com
Tue Jul 19 21:50:07 UTC 2011


On Tue, Jul 19, 2011 at 02:33:27PM -0700, Kevin Oberman wrote:
> On Tue, Jul 19, 2011 at 1:41 PM, Alexander Leidinger
> <Alexander at leidinger.net> wrote:
> > On Mon, 18 Jul 2011 16:41:24 -0700 Jeremy Chadwick
> > <freebsd at jdc.parodius.com> wrote:
> >
> >> But the currently "known method" is to use gnop(8). ?Here's an
> >> example:
> >>
> >> http://www.leidinger.net/blog/2011/05/03/another-root-on-zfs-howto-optimized-for-4k-sector-drives/
> >>
> >> Now, that's for ZFS, but I'm under the impression the exact same is
> >> needed for FFS/UFS.
> >
> > Info: gnop will not work for FFS/UFS because gnop is a temporary
> > solution (needs to be done by hand at each reboot). For FFS/UFS you
> > need to align the slice/partition and chose a good blocksize/fragsize
> > combination (e.g. 32k/4k).
> >
> > Bye,
> > Alexander.
> >
> > --
> > http://www.Leidinger.net ? ?Alexander @ Leidinger.net: PGP ID = B0063FE7
> > http://www.FreeBSD.org ? ? ? netchild @ FreeBSD.org ?: PGP ID = 72077137
> >
> 
> Thanks, Alexander.
> 
> This is what I had expected after reading the man pages, though I
> would think -b 65560 -f 8192' would be a bit more reasonable in this
              ^^^^^^^^
              ^^^^^^^^

Where did this number come from?  Did you mean 65536?  65560 would not
be properly aligned.

> day of bloated file formats. it's been years since I have hit a
> problem with lack of inodes. Probably around 1993 on an old
> SparcStation 1 running SunOS and then only due to a bad assumption I
> made when 'newfs'ing it.
> 
> Again, thanks for the advice. At very least it will save me a bit of time!

Agreed -- thanks for the advice, Alexander.

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                   Mountain View, CA, US |
| Making life hard for others since 1977.               PGP 4BD6C0CB |



More information about the freebsd-stable mailing list