Re: [9fans] IDE FS failure

[Geoff Collyer <geoff@collyer.net>]

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

It looks like you're right; my apologies for the bad advice.  I
remembered that all the startsb block numbers had been corrected (to
"2") in 4e but had forgotten about firstsb (and I'd initialised it in
my file servers to "2").  firstsb (if non-zero) is primarily an
optimisation and it depends on the specific jukebox and on time, so in
either /sys/src/fs/emelie/9pcfs.c or /sys/src/fs/sony/9sonyfs.c,

	conf.firstsb = 13219302;

is presumably wrong (I'd bet on 9sonyfs.c being wrong) and could be
deleted or changed to

	conf.firstsb = 0;

Also, /sys/src/fs/words should probably be amended to advise zeroing
firstsb in the spun-off subtree's 9*fs.c.

I noticed just now that conf.wcpsize is not used in 4e; it was used in
3e in /sys/src/fs/port/worm.c in wcpinit(), but worm.c is now gone.
So all those

	conf.wcpsize = 10;

lines in /sys/src/fs/*/9*fs.c and

	port/main.c:	conf.wcpsize = 1024*1024;

can be deleted.

[-- Attachment #2: Type: message/rfc822, Size: 2440 bytes --]

From: David Swasey <swasey@cs.cmu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] IDE FS failure
Date: Wed, 25 Sep 2002 09:15:11 -0400
Message-ID: <a6e7e85c0618745ab14cb05bbc3c8f91@cs.cmu.edu>

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