Re: GEOM: gpt partitions on a gmirror array possible?
From: Chris Hedley (cbh-freebsd-current_at_groups.chrishedley.com)
Date: 11/30/04
- Previous message: Michal Mertl: "Re: enhacement to mdmfs"
- In reply to: Marcel Moolenaar: "Re: GEOM: gpt partitions on a gmirror array possible?"
- Next in thread: Marcel Moolenaar: "Re: GEOM: gpt partitions on a gmirror array possible?"
- Reply: Marcel Moolenaar: "Re: GEOM: gpt partitions on a gmirror array possible?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 30 Nov 2004 15:37:52 +0000 (GMT) To: Marcel Moolenaar <marcel@xcllnt.net>
On Mon, 29 Nov 2004, Marcel Moolenaar wrote:
> On Mon, Nov 29, 2004 at 02:38:25PM +0100, Pawel Jakub Dawidek wrote:
>>
>> It is because GEOM_GPT class only allow to create GPT labels on rank#1
>> providers (i.e. disks). I'm not sure why we have this hack, maybe marcel@
>> knows something more (cc'ed).
>
> It's there, because it was there for the MBR class when I used that
> class as a blueprint for implementing GPT support. Since GPT is not
> allowed within an MBR slice, or within a GPT partition (no nesting),
> not to mention all the non-native partitioning schemes that GEOM
> supports, that test made sure we only tasted GPT partitions on the
> one kind of providers that existed besides slicers: disks.
>
> I guess a change like geom_mbr.c:1.57 is in order, or a more to-the-
> point test for rejecting GPT on MBR or GPT on GPT.
Thanks for the quick responses, guys. While the great and good are
considering it, I may in the meantime throw caution to the wind and see if
I can make some appropriately ad hoc changes to my own system. Any
suggestions before I start butchering the file in question? Maybe since I
no longer need more than 7 partitions per logical volume I should go back
to using bsdlabel for the time being, although that feels too much like
taking the easy way out. :)
Chris.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Michal Mertl: "Re: enhacement to mdmfs"
- In reply to: Marcel Moolenaar: "Re: GEOM: gpt partitions on a gmirror array possible?"
- Next in thread: Marcel Moolenaar: "Re: GEOM: gpt partitions on a gmirror array possible?"
- Reply: Marcel Moolenaar: "Re: GEOM: gpt partitions on a gmirror array possible?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: Installing onto a >2TB drive
... currently supports booting off of a gpt labeled device. ... EFI firmware
can boot from a GPT ... that first introduced the GPT partition table structure,
... (comp.os.linux.hardware) - Re: GEOM: gpt partitions on a gmirror array possible?
... class as a blueprint for implementing GPT support. ... allowed within an MBR
slice, or within a GPT partition, ... one kind of providers that existed besides
slicers: disks. ... (freebsd-current) - Re: Installing onto a >2TB drive
... currently supports booting off of a gpt labeled device. ... EFI firmware can
boot from a GPT ... that first introduced the GPT partition table structure, ...
since the number of amd64/Core Duo machines>> the number of Itanic ... (comp.os.linux.hardware) - Re: Installing onto a >2TB drive
... currently supports booting off of a gpt labeled device. ... EFI firmware can
boot from a GPT parition table using ELILO. ... (It was the EFI firmware specification
that first introduced the GPT partition table structure, ... (comp.os.linux.hardware) - Re: Dell Perc 6 disk geometry problem with RAID5 (both 6.3 final and 7.0 RC1)
... to partition disks) have problems with volumes larger than 2TB. ... best solved
with having a separate - smaller - boot volume where the OS ... You must use gpt
and not fdisk on any disk, be it a single drive or a virtual disk on a RAID setup that are bigger
than 2TB. ... (freebsd-stable)