WARNING: Expected rawoffset 0, found 63 ?

[Poul-Henning Kamp]

In message <1096056348.9306.87.camel at zappa.Chelsea-Ct.Org>, Paul Mather writes:
>On Fri, 2004-09-24 at 15:19, Chris Elsworth wrote:
>
>> app1# bsdlabel -r /dev/mirror/gm
>> # /dev/mirror/gm:
>> 8 partitions:
>> #        size   offset    fstype   [fsize bsize bps/cpg]
>>   a: 71119675       16    unused        0     0
>>   c: 71119691        0    unused        0     0         # "raw" part, don't edit
>> 
>> 
>> So now another two things crop up - where has that a partition come from
>> (perhaps that's just what bsdlabel -w does by default, no big deal)
>> but more importantly, why do they both have an offset of 16 bytes..
>> It didn't seem to mind me changing it to zero, though. So now I'll see
>> if I can get it booting :)
>
>I believe the above is bsdlabel's idea of an "auto" label.  I don't know
>why the 16 sector offset for the "a" partition, because you don't get
>that when you label a slice via sysinstall and choose the "auto
>defaults."  (Maybe there's a case for making bsdlabel's "auto" label
>behave the same as sysinstall.)

The 16 offset is to protect the disklabel and boot code.  You have no
idea how much I hate the person who made the hack to leave the metadata
inside the trafic partitions.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.