Date: Sat, 14 Aug 2010 21:57:54 +0200 From: Dick Hoogendijk <dick@nagual.nl> To: freebsd-questions@freebsd.org Subject: Re: ZFS not usable on FreeBSD-8.1 Message-ID: <4C66F542.6090501@nagual.nl> In-Reply-To: <19558.60756.860555.968721@gargle.gargle.HOWL> References: <4C669668.5040906@nagual.nl> <19558.60756.860555.968721@gargle.gargle.HOWL>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14-8-2010 21:24, George Hartzell wrote: > You haven't provided enough information for me to make a concrete > suggestion, but this kind of thing often seems to boil down to > something getting confused over slices and partitions when they both > have the same extent (start->end) on disk. This used to bite me in > the gmirror world until I learned to make the partition one block > smaller than the slice it lived in. And how do I make the partition precisely one block smaller than the slic it lives in? How do I know what the "blocksize" is? > Are you using explicit device names to add the disks to your pool? If > so you'll gain robustness by using labels, either glabels as described > here: > > http://submesa.com/data/bsd/zfs > > or if you're in the gpt world then gpt labels as described in the > gpart commands illustrated here: > > http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror I tried both methods. I had the disks as GPT labeld ones and slices by sysinstall. None worked. So it may be the one block difference. Please tell me how to do that.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C66F542.6090501>