From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200202282106.g1SL6n618494@copernicus.cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs config problem status update (still unsolved)
In-reply-to: Your message of "Fri, 22 Feb 2002 19:39:35 +0100."
             <200202221839.g1MIdaR09315@copernicus.cs.utwente.nl> 
References: <20020222122536.A643419A6E@mail.cse.psu.edu> 
 <200202221255.g1MCt3q02259@copernicus.cs.utwente.nl> 
 <200202221839.g1MIdaR09315@copernicus.cs.utwente.nl>
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Feb 2002 22:06:49 +0100
Topicbox-Message-UUID: 5c76f47e-eaca-11e9-9e20-41e7f4b1d025

Hoping this still doesn't bore to much, yet another short update.
Status: not solved yet.

I have added an ide disk containing a stand-alone plan 9
installation to the fs pc, and can look at the /dev/sd*/data.
On the worm I can see strings that look like data, and at
(just after the start of) the cache I see the configuration.
Would there be a way (not too involved) to extract that part
of the fs code that 'parses' the on-disk data,
to interpret it (and so see whether/where the(re) problems are)?
Or could I use pieces of kfs?

Wrt things I noticed previously:
when I do 'p /dev/sd00/data' I see the config data -
and indeed there appears a single-character error
(filsss instead of filsys, or something similar).

Is the ide-patched fs kernel 'compatible' with the plan9pc one?
Or do the on-disk structures differ (w.r.t. 'using 16K blocks') 

Thanks,
Axel.