Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 23 Jan 2013 22:18:52 +1100
From:      Peter Jeremy <peter@rulingia.com>
To:        Michael DeMan <freebsd@deman.com>
Cc:        FreeBSD Filesystems <freebsd-fs@freebsd.org>
Subject:   Re: RFC: Suggesting ZFS "best practices" in FreeBSD
Message-ID:  <20130123111852.GM30633@server.rulingia.com>
In-Reply-To: <AAE9CC17-B5C4-43DC-B86B-2F498FCA5AD4@deman.com>
References:  <314B600D-E8E6-4300-B60F-33D5FA5A39CF@sarenet.es> <AAE9CC17-B5C4-43DC-B86B-2F498FCA5AD4@deman.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--SLfjTIIQuAzj8yil
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2013-Jan-22 17:27:13 -0800, Michael DeMan <freebsd@deman.com> wrote:
>- probably there are enough people even though it seems pretty obvious in =
a couple more years nobody will have 32-bit or less than 8GB RAM?

FreeBSD goes into an awful lot of embedded devices which are unlikely
to transition off 32-bit or have more than a few hundred MB RAM for
the foreseeable future.  Definitely, the PC world is going that way -
but it's heavily driven by Microsoft and it's quite likely that the
next version of Windows won't fit into 32-bits.

>I could be disinformed here, but my understanding) is best practice is to =
use gpart + gnop to:
>#1.  Ensure proper alignment for 4K sector drives - the latest western dig=
itals still report as 512.

Recent versions of ZFS allow you to specify ashift=3D12 without needing
gnop.  And in any case, gnop is only needed when you initialise the
pool.  Once the initial ashift value is set, it can't be changed.
(And I'd be interested in knowing how well a SSD ZIL compensates for
having an ashift=3D9 pool on 4K sector disks).

>#2.  Ensure a little extra space is left on the drive since if the whole d=
rive is used, a replacement may be a tiny bit smaller and will not work.

As someone else has mentioned, recent ZFS allows some slop here.  But
I still think it's worthwhile carving out some space to allow for a
marginally smaller replacement disk.

>#3.  Label the disks so you know what is what.
With a paper label and a pen.

>ZFS GENERAL BEST PRACTICES - address the regular ZFS stuff here=20
>- why the ZIL is a good thing even you think it kills your NFS performance
>- no vdevs > 8 disks, raidz1 best with 5 disks, raidz2 best with 6 disks, =
etc.
>- striping over raidz1/raidz2 pools
>- striping over mirrors
>- etc...

Most of this can be pointers to generic ZFS documentation.  Which brings
up another point - the documentation should make it clear whether a
particular hint is FreeBSD-specific or generic across all ZFS platforms.
And what "generic" ZFS hints are unnecessary on FreeBSD.

--=20
Peter Jeremy

--SLfjTIIQuAzj8yil
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAlD/xxwACgkQ/opHv/APuIeUFACfc9Nsr1d6RtSfgcGmtXTrRCd/
uTsAn2LBwgWuMbR8sxwUFcA9dAjKSz+K
=vLtP
-----END PGP SIGNATURE-----

--SLfjTIIQuAzj8yil--



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