From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200203281821.g2SILQE13075@copernicus.cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Solved! (was: Re: [9fans] fs partwrite)
In-reply-to: Your message of "Tue, 05 Mar 2002 11:14:02 +0100."
             <200203051014.g25AE3c24107@copernicus.cs.utwente.nl> 
References: <20020302092921.C17C519A7F@mail.cse.psu.edu> 
 <200203051014.g25AE3c24107@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 Mar 2002 19:21:26 +0100
Topicbox-Message-UUID: 6f0870ae-eaca-11e9-9e20-41e7f4b1d025

Just to keep you informed :-)
Today I had finally time again for this problem.

I tried config
   filsys main cp(w0)0.50f(w1.<0-1>.0)
   filsys dump o
   filsys temp p(w0)50.50
and the problems seem to be gone
(and this config is now nicely documented in the 9fans mail archive :-)

I issued 'check' commands for main and temp,
and they did not find errors given this config
(they did report problems for the previous config, listed below --
 part(read/write)? errors for main, and a panic for temp
 (forgot actual error message))
Now, for temp I also issued 'check rdall' which succeeded,
so I suppose, finally, 'problem closed'!

Thanks to all who helped and offered support!

Regards,
Axel.

> 
> > it's more likely that there's something wrong with the
> > configuration.  what was it?
> 
> I'm now typing from memory (got details down on paper and
> on the disk -- indeed I succeeded on browsing the disk using
> xd/od on the data partition)
> 
>   filsys main cp(w0)0.25f(w1.<0-1>.0)
>   filsys dump o
>   filsys temp p(w0)25.75
> 
> > of course, one advantage of posting it here is that if
> > you lose it again, you can get it from the list!
> agreed! :-)  (even from my own outbox)