Re: [9fans] KFS Crash

["Mark C. Otto" <Mark_Otto@FWS.Gov>]

Booting up with the install disk, I was able to get a window under rio.  I could
not start kfs though:

% disk/kfs -f /dev/sdC0/fs
File system main inconsistent
Would you like to ream it (y/n)?  hell no. tag = <badtag>; expected Tdir
kfs init 496: FID1 attach to root

# The root of the problem is at the root.  Russ is right:  at least it asks
before
# wiping out your file system.

mount /srv/kfs /n/kfs
mount: sys: write on closed pop pc=0x00003abe

I can get to the 9fat file system.  I can probably reconstruct most of what I
lost expect for a few mail messages and my plan9 wish list.  I'm sure all the
important things will come back to me. :)

For the autopsy, I have always run disk/kfscmd halt to shut the system down
except for the few times the system locked up.  I have never run disk/kfscmd
check.  I have 500mb disk and had just installed wiki and pq.  (I didn't install
TeX for space reasons.)  That may have nearly filled the disk.  I haven't run
Russ's df in a while, so I won't be able to confirm that.  It did get some 9p
and bad address errors before it locked up.  I should have had a plan before I
rebooted the final time.  Next time I might use Rob's rio crash fall back
procedure.


To debug rio after it's crashed:
1. If you have a shell prompt, hit carriage return until every one gets you a
shell prompt; that means the rio process holding the keyboard open has filled
its
buffer.  Then, although echo will still be off, the shell is all yours.
2. Type
     kill rio|rc
and you'll get echo back and you can restart rio or whatever else
you want to do.

3. After that run the disk diagnostics and rebuild the disk

 disk/kfscmd -r check
 disk/kfscmd -fdtw check  # I'm guessing at the options from kfscmd(8)


Guess this is the kick to usurp another old pc for a cpu/auth server, set up
dhcpd(8), and u9fs on my linux box.  Unfortunately, I have JMK's disliked
Adaptec SCSI controllers (AHA-2940U2/AHA-2940U2W PCI and AIC-7880 PCI), so I
can't set up a real file server yet.

Russ, Rob, and Scott thanks for helping me at least find out what state my
system is in.

Mark