Date: Sat, 26 Mar 2011 01:15:57 -0500 From: Adam Vande More <amvandemore@gmail.com> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-fs@freebsd.org Subject: Re: tying down adaX to physical interfaces Message-ID: <AANLkTik1xP3VKPfOR6SkzhjFMCOfgynCKZZ0zS7P-p9u@mail.gmail.com> In-Reply-To: <20110326051643.GA43364@icarus.home.lan> References: <AFDA19F9-DC78-463D-862D-6E4F3CB2C2C3@deman.com> <20110326003818.GT78089@deviant.kiev.zoral.com.ua> <D665B3EE-34D6-4125-A9C1-06C71548F7F5@deman.com> <20110326051643.GA43364@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 26, 2011 at 12:16 AM, Jeremy Chadwick <freebsd@jdc.parodius.com>wrote: > I've mentioned this before -- and I'm certain others will point out that > said problem was fixed, etc. etc. (done so before, and I've simply > forgotten) -- but there are complexities introduced into the fray when > using glabel(8) and similar utilities. There have been complaints on > the lists about it. I've had a very, very long week and can't be > bothered to dig up the evidence; sorry. > FWIW, I believe you are referring to geom metatdata/GPT secondary table conflict. If you put a label on a GPT partition, it will overwrite it's backup GPT table. You'd want to do something like glabel the raw device,eg ada0 then create GPT partitions on the resulting device. This setup works fine, but is going to be a FreeBSD specific disk. Just using a GPT label on partition that spans the entire device may be more desirable depending on needs. -- Adam Vande More
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTik1xP3VKPfOR6SkzhjFMCOfgynCKZZ0zS7P-p9u>