Re: Disk labelling: WARNING: Expected rawoffset 37752750, found 0

> Date: Tue, 06 May 2003 15:12:08 -0700
> From: Lars Eggert <larse_at_ISI.EDU>
> Sender: owner-freebsd-current_at_freebsd.org
> 
> This is a cryptographically signed message in MIME format.
> 
> --------------ms020908070307010703090709
> Content-Type: text/plain; charset=us-ascii; format=flowed
> Content-Transfer-Encoding: 7bit
> 
> Poul-Henning Kamp wrote:
> > 
> >>2) Does the "WARNING: Expected rawoffset 37752750, found 0" spell
> >>  trouble ahead, and if so, what should I do to fix it?
> > 
> > It should be harmless.
> > 
> > I would be very interested if you could try to compile the "bsdlabel"
> > program in src/sbin/bsdlabel and tell me what that says about your
> > disk.
> 
> I'm seeing this, too:
> 
> [root_at_nik: /etc] dmesg | grep raw
> WARNING: Expected rawoffset 63, found 0
> WARNING: Expected rawoffset 63, found 0
> WARNING: Expected rawoffset 63, found 0
> WARNING: Expected rawoffset 50331645, found 0
> 
> bsdlabel and disklabel show the exact same output for all disks, e.g.
> 
> [root_at_nik: ~] disklabel /dev/da0s1
> # /dev/da0s1:
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>    a:  8388608        0    4.2BSD     2048 16384 28512
>    c: 50331582        0    unused        0     0         # "raw" part, 
> don't edit
>    d:  8388608  8388608    unused        0     0
>    e:  4194304 16777216    unused        0     0
>    f: 29360062 20971520    unused        0     0
> 
> [root_at_nik: ~] bsdlabel /dev/da0s1
> # /dev/da0s1:
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>    a:  8388608        0    4.2BSD     2048 16384 28512
>    c: 50331582        0    unused        0     0         # "raw" part, 
> don't edit
>    d:  8388608  8388608    unused        0     0
>    e:  4194304 16777216    unused        0     0
>    f: 29360062 20971520    unused        0     0
> 
> Could it have something to do with ccd? I stripe the d, e and f 
> partitions together with their counterparts on da1 for /var, /tmp and /usr.

Nope. I was not using ccd. I did see a patch to fix this was put into
CVS an hour or two ago and it called the message spurious in the
comment. Said that the value was being fetched from the wrong place, I
think.

In any event, I suspect it's now fixed.

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman_at_es.net			Phone: +1 510 486-8634