Craig Boston wrote: > On Thu, Jan 19, 2006 at 02:53:42PM +0000, Thomas Hurst wrote: >>> IIRC I had the problem that 'gmirror insert' without '-h' not always >>> inserted the slice specified by the entire block device (e.g. >>> /dev/ad4s1 vs. /dev/ad4). Apparently there is some auto detection >>> code and/or gmirror cannot differ correctly, but that's just a >>> guess. Specifing '-h' fixed it in my case. >> >> As I understand it, gmirror writes its metadata on the last sector of >> the provider; when tasting devices it will look at the last sector of >> ad4, find the metadata and use that as the provider for your mirror; >> you can either hardcode the provider name there to override it, or >> make the slice 1 sector smaller so gmirror tastes ad4, finds >> nothing, then goes on to taste ad4s1 correctly. > > This was fixed for most cases by adding the size of the provider to > the metadata. ad4 should be a different size than ad4s1 as the > partition table has to go somewhere... > > Looks like it was fixed in HEAD in Feb 2005, and MFC'd to 5.x in > March. Shouldn't have ever been a problem for 6.x release. > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/geom/mirror/g_mirror.c#rev1.19 .2.8 > Hrm. With using the method for slices as specified on the ~rse page, I got repeatable lockups.
With specifying the entire disk, it works as normal, but no dump device. Suggestions on how to enable dump, **AND** reliable boot would be appreciated. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"