8.0-B4 gstripe / GEOM_PART_* upgrade woes

[Stephen Hurd]

Ivan Voras wrote:
> An interesting problem. I presume that in either case (gpart or 
> GEOM_BSD/MBR) the output of "gstripe status" is the same? Only the 
> interpretation of the partition tables is problematic?

Yes, but the output of gstripe list is different in the mode lines... 
for GEOM_PART, the mode is r0w0e0 in all consumers and for GEOM_*, the 
mode is r3w3e5.

> What is the expected ("good") structure of the partitions/file 
> systems? Do you have a single MBR partition and inside it multiple BSD 
> partitions? What are their partition types?

Not sure the correct way to get the info, but the output of fdisk and 
bsdlabel follow:
==== START of fdisk ====
 > fdisk /dev/stripe/raid0
******* Working on device /dev/stripe/raid0 *******
parameters extracted from in-core disklabel are:
cylinders=5219 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=5219 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
<UNUSED>
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 0, size 50000 (24 Meg), flag 80 (active)
        beg: cyl 0/ head 0/ sector 1;
        end: cyl 1023/ head 254/ sector 63
==== END OF fdisk ====

==== START OF bsdlabel ====
 > bsdlabel /dev/stripe/raid0
# /dev/stripe/raid0:
8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a: 16777216       16    4.2BSD     2048 16384 28552
  b: 16777216 16777232    4.2BSD     2048 16384 28552
  c: 20964825  8385930    unused        0     0         # "raw" part, 
don't edit
  d: 50302960 33554448    4.2BSD     2048 16384 28552
bsdlabel: partition c doesn't start at 0!
bsdlabel: partition c doesn't cover the whole unit!
bsdlabel: An incorrect partition c may cause problems for standard 
system utilities
==== END OF bsdlabel ====

Now that I look at the bsdlabel output, I vaugely recall that I couldn't 
get c correct...