Date: Wed, 27 Feb 2013 14:44:10 +0100 From: Borja Marcos <borjam@sarenet.es> To: John <jwd@FreeBSD.org> Cc: FreeBSD Filesystems <freebsd-fs@freebsd.org> Subject: Re: RFC: Suggesting ZFS "best practices" in FreeBSD Message-ID: <E6A5220B-7C62-420D-956B-83DC11D2E8BD@sarenet.es> In-Reply-To: <20130226204258.GA62875@FreeBSD.org> References: <314B600D-E8E6-4300-B60F-33D5FA5A39CF@sarenet.es> <AAE9CC17-B5C4-43DC-B86B-2F498FCA5AD4@deman.com> <20130123111852.GM30633@server.rulingia.com> <CACpH0MfpF65N9hHxD9o6UYjF9BGWF3TAUj004tWDxq-oX-N1Vg@mail.gmail.com> <20130226204258.GA62875@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 26, 2013, at 9:42 PM, John wrote: > And of course, if you look through the source, you'll see where ZFS > makes a distinction between slices & whole disks. I have not debugged > through it recently to see how much of it is currently in use. >=20 > If you use dual-channel SAS drives with geom multipath, you need to = be > clear whether your meta-data on disk from the different geoms = collide...=20 >=20 > Regardless of how the best practices is put together, make sure > folks are aware of the limitations/caveats of the different choices. Exactly. Anyway, as far as I know, both FreeBSD and Solaris should be = able to work with GPT slices instead of whole disks.=20 In the past at least (and, despite the lore one can read here and there) = Solaris refused to use the disks cache if the vdevs were made of slices instead of whole disks, but maybe it has changed in = the past. As far as I know, however, FreeBSD doesn't show that behavior. Borja.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E6A5220B-7C62-420D-956B-83DC11D2E8BD>