Re: [9fans] fossil failure question

[jmk@plan9.bell-labs.com]

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