gmirror confusion

[Pawel Jakub Dawidek]

On Sun, Dec 12, 2004 at 04:50:12PM -0700, Ken Gunderson wrote:
+> I'll be lame and follow up my own post...  First, sorry that I confused 
+> "provider" with "consumer", so that question is moot.  However, I note 
+> the following:
+> 
+> >>>>>>>
+> build# bsdlabel mirror/mirror0s1
+> # /dev/mirror/mirror0s1:
+> 8 partitions:
+> #        size   offset    fstype   [fsize bsize bps/cpg]
+>   a:   524288        0    4.2BSD     2048 16384 32776
+>   b:  4194304   524288      swap
+>   c: 78156162        0    unused        0     0         # "raw" part, 
+> don't edit
+>   d:  1048576  4718592    4.2BSD     2048 16384     8
+>   e:  1048576  5767168    4.2BSD     2048 16384     8
+>   f:  8388608  6815744    4.2BSD     2048 16384 28552
+>   g: 16777216 15204352    4.2BSD     2048 16384 28552
+>   h: 46174594 31981568    4.2BSD     2048 16384 28552
+> 
+> build# bsdlabel /dev/mirror/mirror0s1
+> # /dev/mirror/mirror0s1:
+> 8 partitions:
+> #        size   offset    fstype   [fsize bsize bps/cpg]
+>   a:   524288       63    4.2BSD     2048 16384 32776
+>   b:  4194304   524351      swap
+>   c: 78156162       63    unused        0     0         # "raw" part, 
+> don't edit
+>   d:  1048576  4718655    4.2BSD     2048 16384     8
+>   e:  1048576  5767231    4.2BSD     2048 16384     8
+>   f:  8388608  6815807    4.2BSD     2048 16384 28552
+>   g: 16777216 15204415    4.2BSD     2048 16384 28552
+>   h: 46174594 31981631    4.2BSD     2048 16384 28552
+> partition c: partition extends past end of unit
+> bsdlabel: partition c doesn't start at 0!
+> bsdlabel: An incorrect partition c may cause problems for standard 
+> system utilities
+> partition h: partition extends past end of unit
+> <<<<<<<<<<<<<<<<<<<
+> 
+> Per man page for bsd label:
+> 
+> "When specifying the device, the /dev/ path prefix may be omitted; the      
+> bsdlabel utility will automatically prepend it."
+> 
+> Hence I was getting confused about seeming eratic bsdlabels, until I 
+> figured out that the return was consistent, but dependent upon whether 
+> I prepended "/dev" or not, at least when applied to gmirror provider.  
+> Is this 1) a bsdlabel or gmirror issue, and 2) which return should I 
+> believe?

Argh! I just found your mail.
This is a bug in bsdlabel(8). Could you try this patch:

	http://people.freebsd.org/~pjd/patches/bsdlabel.patch

-- 
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd at FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-geom/attachments/20050105/eb78a3dc/attachment.bin