From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] file server trouble
From: anothy@cosym.net
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Message-Id: <20020403164150.3E2F319A55@mail.cse.psu.edu>
Date: Wed,  3 Apr 2002 11:39:44 -0500
Topicbox-Message-UUID: 726c1dea-eaca-11e9-9e20-41e7f4b1d025

thanks to geoff's pointers, i was able to build a kernel that
correctly recovered my file system. the file server is back
up, and stays running in the face of normal use. but things
still arn't "right". i'm now getting lots of messages of the
following form on my file server console:

fworm: write 152116
cwio: write induced dump error - w worm
fworm: write 152117
cwio: write induced dump error - w worm
fworm: write 152151
cwio: write induced dump error - w worm
fworm: write 152152
cwio: write induced dump error - w worm

this started after a dump was attempted. the above block
would repeat every few seconds (~10). after the next
dump, a new set was generated, with about twice the
number of errors, printing about ever 20 seconds. this
looks to me like a bad disk (which is really annoying, since
it's a few months old). do others agree?

between now and when i can get the disk replaced, is
there any mechanism in the fs kernel for marking blocks
"bad"? and if not, am i correct in my belief that all my
dumps into the future will be unsafe, since dumps include
all the previous blocks (until modification)?
ア