Date: Thu, 01 Aug 2013 13:06:35 +0930 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: J David <j.david.lists@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: Problem with zfsloader on 9.2-BETA2 Message-ID: <51F9D7C3.7020806@ShaneWare.Biz> In-Reply-To: <CABXB=RR7E2s5GU29ZgU1hBk4MqkvrO95-RBg4TE6ahozP6KmCg@mail.gmail.com> References: <CABXB=RRhVDdKCidwnrji1qR41Rx7uvs2Lx1ZPF1FREOHcnm5bg@mail.gmail.com> <alpine.BSF.2.00.1307311107240.1327@mail.fig.ol.no> <CABXB=RR7E2s5GU29ZgU1hBk4MqkvrO95-RBg4TE6ahozP6KmCg@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On 01/08/2013 01:42, J David wrote: > => 34 1953525101 da2 GPT (931G) > 34 222 - free - (111k) > 256 1953508495 1 freebsd-zfs (931G) > 1953508751 16384 9 !6a945a3b-1dd2-11b2-99a6-080020736631 (8.0M) > > da3 - da7 are identical to da2. > > So maybe it's a little weird that our boot blocks are on our > ZLOG/L2ARC devices, rather than our data devices? > I think that 8M partition looks weird. It looks like a leftover from a previous config? Two things I would think to consider - the odd alignment of the partition. Most recent drives benefit from 4K alignment. For the last couple of years drives have started using 4K blocks instead of the traditional 512byte blocks. They still accept 512byte blocks and internally remap to the 4K blocks with a penalty. google 4k partition alignment for a variety of discussions. Secondly do you need that trailing 8M? I would give zfs the entire drive and not use partitions.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51F9D7C3.7020806>