From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ec2afa550d631ed498bc710e9d7c5d77@terzarima.net>
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kfs locks
In-Reply-To: <200403072003.i27K3noh080998@adat.davidashen.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Sun,  7 Mar 2004 20:12:17 +0000
Topicbox-Message-UUID: 1fe98686-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.
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,
and there were changes in chk in november (for instance), although
they look benign.  i thought i'd like to know more about the
actual cause of wrenwrite errors before trying to guess what and
where the problem might be!