From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Tolpin Message-Id: <200403072020.i27KKcAN081068@adat.davidashen.net> To: 9fans@cse.psu.edu Subject: Re: [9fans] kfs locks In-Reply-To: Content-Type: text/plain; charset=KOI8-R Date: Mon, 8 Mar 2004 00:20:38 +0400 Topicbox-Message-UUID: 1fef4f4e-eacd-11e9-9e20-41e7f4b1d025 > 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.