Date: Sun, 04 Dec 2011 02:28:24 -0800 From: perryh@pluto.rain.com To: cyberleo@cyberleo.net Cc: ryallsd@gmail.com, freebsd-questions@freebsd.org, lists@midsummerdream.org Subject: Re: AHCI driver and static device names Message-ID: <4edb4b48.LvOhZvvsP1inJeps%perryh@pluto.rain.com> In-Reply-To: <4EDA56A3.6090108@cyberleo.net> References: <4ED98E9F.9010401@midsummerdream.org> <CAN3mi_2u%2BHwFf3m%2BxvsNncfNpj_rFp94xjAv%2Bf0eFT7c4a%2B8Tg@mail.gmail.com> <4EDA489B.9060503@midsummerdream.org> <4EDA56A3.6090108@cyberleo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
CyberLeo Kitsana <cyberleo@cyberleo.net> wrote: > You cannot combine GPT with glabel (or any other geom class > that writes data to the first or last 34 sectors of a disk, > like gmirror) due to layout conflicts. This is overstated. Since a GPT ordinarily is intended to be booted from, and so must be recognized by the BIOS, it must be written directly on the actual drive -- the "rank 1 provider" in GEOM terms -- because that is the only way for the GPT metadata to be located where the BIOS expects to find it (at both the beginning and the end of the drive). It is, however, possible to combine GPT with gmirror, gjournal, etc. by using GPT partitions, rather than drives, as providers for the other geoms. For example, create a mirror from ad0p1 and ad2p1 rather than from ad0 and ad2. Similarly, it "should" be possible to glabel a GPT partition -- although this seems unlikely to be useful in practice since GPT provides its own labelling scheme.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4edb4b48.LvOhZvvsP1inJeps%perryh>