[9fans] fossil failure question

[9fans] fossil failure question

[Ronald G. Minnich]

This is on Xen; I'm willing to blame xen, but many other things are
working. I'm trying to do the kfs->fossil transition. I have /dev/sd00/fs
and /dev/sd01/fossil, fossil mounted as /n/fossil, kfs as /n/kfs.

I'm doing the mkfs|mkext s dance as found on the wiki.

disk/mkfs -a -s /n/kfs /sys/lib/sysconfig/proto/allproto |
	disk/mkext -u -d /n/fossil

At some point in fossil console I get 300 or these:
main: labelUnpack ff ff 6ccd6c27 01000000 0001ffff
labelUnpack ff ff 6ccd6c27 01000000 0001ffff
labelUnpack ff ff 6ccd6c27 01000000 0001ffff
labelUnpack ff ff 6ccd6c27 01000000 0001ffff
labelUnpack ff ff 6ccd6c27 01000000 0001ffff
labelUnpack ff ff 6ccd6c27 01000000 0001ffff
labelUnpack ff ff 6ccd6c27 01000000 0001ffff
labelUnpack ff ff 6ccd6c27 01000000 0001ffff
labelUnpack ff ff 6ccd6c27 01000000 0001ffff
labelUnpack ff ff 6ccd6c27 01000000 0001ffff
.
.
.
.


Is this an error (I'm guessing yes)
What's it mean?
What's a good place to start digging to see what's going on?

thanks

ron

Re: [9fans] fossil failure question

[jmk]

that looks like you are either not reading or writing the data
correctly (once you initialise the fossil the labels should all be 0
i think).

perhaps there's interference in the driver between discs, e.g.
we don't have locking right or have some piece of state which
is shared between the drives when it shouldn't be.

also, check the disc size, etc. is right.

--jim

On Thu Mar  3 14:20:53 EST 2005, rminnich@lanl.gov wrote:
>
> This is on Xen; I'm willing to blame xen, but many other things are
> working. I'm trying to do the kfs->fossil transition. I have /dev/sd00/fs
> and /dev/sd01/fossil, fossil mounted as /n/fossil, kfs as /n/kfs.
>
> I'm doing the mkfs|mkext s dance as found on the wiki.
>
> disk/mkfs -a -s /n/kfs /sys/lib/sysconfig/proto/allproto |
> 	disk/mkext -u -d /n/fossil
>
> At some point in fossil console I get 300 or these:
> main: labelUnpack ff ff 6ccd6c27 01000000 0001ffff
> labelUnpack ff ff 6ccd6c27 01000000 0001ffff
> labelUnpack ff ff 6ccd6c27 01000000 0001ffff
> labelUnpack ff ff 6ccd6c27 01000000 0001ffff
> labelUnpack ff ff 6ccd6c27 01000000 0001ffff
> labelUnpack ff ff 6ccd6c27 01000000 0001ffff
> labelUnpack ff ff 6ccd6c27 01000000 0001ffff
> labelUnpack ff ff 6ccd6c27 01000000 0001ffff
> labelUnpack ff ff 6ccd6c27 01000000 0001ffff
> labelUnpack ff ff 6ccd6c27 01000000 0001ffff
> .
> .
> .
> .
>
>
> Is this an error (I'm guessing yes)
> What's it mean?
> What's a good place to start digging to see what's going on?
>
> thanks
>
> ron

Re: [9fans] fossil failure question

[Russ Cox]

> > labelUnpack ff ff 6ccd6c27 01000000 0001ffff

Your disk is corrupt.  This isn't anything like a valid label.
The first four numbers should all be small integers,
and the last one should be 0, 1, 2, or random >= 32.

I'd probably put prints in diskReadRaw and diskWriteRaw
giving the partition, offset, and data read/written, and
log all that to a file and then look carefully at it.
I suspect the Xen disk device driver.

Russ

Re: [9fans] fossil failure question

[Ronald G. Minnich]

On Thu, 3 Mar 2005 jmk@plan9.bell-labs.com wrote:

> perhaps there's interference in the driver between discs, e.g.
> we don't have locking right or have some piece of state which
> is shared between the drives when it shouldn't be.

It might be that.


> also, check the disc size, etc. is right.

that is ok as far as I can tell.

ron

Re: [9fans] fossil failure question

[Ronald G. Minnich]

On Thu, 3 Mar 2005, Russ Cox wrote:

> I suspect the Xen disk device driver.

safe bet :-)

thanks, that gives me something to look for.

ron