From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <a6e7e85c0618745ab14cb05bbc3c8f91@cs.cmu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] IDE FS failure
From: David Swasey <swasey@cs.cmu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Wed, 25 Sep 2002 09:15:11 -0400
Topicbox-Message-UUID: f4adfe2c-eaca-11e9-9e20-41e7f4b1d025

If you can compile a new fs kernel using a stand-alone machine, then
you can probably get past this particular panic.  I believe this
happens because of the line

	conf.firstsb = 13219302;

in your file server's localconfinit.  (This function is part of the
file-server-specific .c file; it may be called 9pcfs.c.)

If firstsb is non-zero, then it is the address of the first super
block to consult when performing a recovery; otherwise, the value in
the startsb array (near the top of 9pcfs.c) is used.

I suggest setting firstsb to 0 and recompiling the file server kernel.
With the new kernel, "recover main" should actually start the recovery
process.

-dave

> On Tue, Sep 24, 2002 at 04:54:03PM -0700, Geoff Collyer wrote:
>>
>> 	recover main
>> 	end
>>
> I get a different error.  I wonder if I didn't configure "archive"
> badly and somehow overlapped it onto main or the cache.  The error is
> now
>
> 	panic: fworm: rbounds 13219302