From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ab9f30bf73186d530b4911d392e0640a@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] i/o error: wrenwrite
From: Richard Miller <rm@hamnavoe.com>
In-Reply-To: <1bd7003f9145bbd201061285adb27b6b@plan9.escet.urjc.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Wed,  3 Mar 2004 09:15:51 +0000
Topicbox-Message-UUID: 0efba2dc-eacd-11e9-9e20-41e7f4b1d025

> When I've seen wrenwrite complaints, it has always been due to
> about-to-fail disks.

An "i/o error" report from wrenwrite is not necessarily a hardware
problem.  It may be a failed seek because a block address in the
filesystem has been corrupted.  This should be repairable (with some
loss of data) by kfscmd chk.

-- Richard