From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <b0fb761c6a2655ac4a242e71faffc440@plan9.bell-labs.com>
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kfs locks
In-Reply-To: <200403072020.i27KKcAN081068@adat.davidashen.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Sun,  7 Mar 2004 22:27:25 -0500
Topicbox-Message-UUID: 202ff6ac-eacd-11e9-9e20-41e7f4b1d025

On Sun Mar  7 15:22:37 EST 2004, dvd@davidashen.net wrote:
> > in a previous message, with various debugging prints turned on
> > and inserted, there seemed to be driver requests to abort a command.
> 
> write is being aborted, because it is asked to write at offset 
> not present on the disk. It looks like the in-memory structure 
> is corrupt.
> 
> > you don't seem to see the problem unless you power cycle,
> > and although i don't use it as much as i did, i still use kfs a
> > fair bit (and i do sometimes just switch off that machine),
> > and i don't see similar problems.
> > now, it's quite likely that i'm running an older version of kfs,
> 
> It is quite likely that your machine is slower. If I slow down
> the kfs or kernel code by inserting more debugging, the problem
> disappears because the structure is flushed before being overwritten.
> 
> > actual cause of wrenwrite errors before trying to guess what and
> > where the problem might be!
> 
> offsets are negative vlongs. 

The offset is supposed to be checked way before getting to the
ATA driver:
1) the write and seek system calls check the offset is not negative;
2) the higher level of the disc driver checks the address requested
   is within the partition.

What does your partition table look like?