From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200303192101.h2JL1R805307@zamenhof.cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil/venti: diskReadRaw failed
In-reply-to: Your message of "Wed, 19 Mar 2003 21:52:52 +0100."
             <200303192052.h2JKqqF05215@zamenhof.cs.utwente.nl> 
References: <fd97175116cec64c5602a90feb4e7487@plan9.bell-labs.com> <200303192052.h2JKqqF05215@zamenhof.cs.utwente.nl> 
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5301.1048107687.1@zamenhof.cs.utwente.nl>
Date: Wed, 19 Mar 2003 22:01:27 +0100
Topicbox-Message-UUID: 81c571aa-eacb-11e9-9e20-41e7f4b1d025

Just remembered that, in an attempt to speed things up,
I had echo-ed 'dma on' and 'rwm on' to /dev/sdD1/ctl .
To be sure, I switched both off, and repeated the cp;
it took longer but the result was the same (i/o error).

I wrote in response to Russ:
> > this is giving you the path from the block with the
> > i/o error all the way back up to the root block.
> > given that 0xf61d is readable yet 0xee65 is not,
> > i'd say you have a real disk error rather than
> > an overflow.
> > 
> > try running cp /dev/sdC0/fossil /dev/null and
> > see if you get i/o errors then.
> 
> term% cp /dev/sdD1/fossil /dev/null
> cp: error reading /dev/sdD1/fossil: i/o error
> 
> Guess that's what you mean.