From: "Mark C. Otto" <Mark_Otto@FWS.Gov>
To: 9fans@cse.psu.edu
Subject: [9fans] KFS Crash
Date: Wed, 14 Feb 2001 16:43:23 -0500 [thread overview]
Message-ID: <3A8AFBFB.2890AF90@FWS.Gov> (raw)
In-Reply-To: <200102010808.AAA00583@tammananny.tiger>
I had bad addresses and 9p message start filling the screen. Rio locked up, and
I didn't see any way to get out of it, so I rebooted. Unfortunately, I couldn't
even boot up, not even with my boot floppy.
kfs...boot: nop...File system main inconsistent
Would you like to ream it (y/n)? tag = <badtag>;Tdir
kfs init 5: FID1 attach to root
boot: read nop: file does not exist
panic: boot process died: unknown
ktrace /kernel/path 8010649e 8026bdb4
8026bd54=801063a3 8026hd64=80171915
...
cpu0: exiting
Looks like I am going to have to reinstall the system, unless my terminal is
just trying to be sympathetic with Russ's. :-( I have the following questions:
1. If rio crashes is there a way to kill rio and get back to the shell?
2. Given that I could, what diagnostics could I run to identify the problem?
3. Is there a way to repair the disk at this point?
4. Given that you don't have much faith in kfs and some of us are using it
exclusively on our standalone terminals, what sort of maintainance, such as
disk/kfscmd check, should we be doing?
Mark
next prev parent reply other threads:[~2001-02-14 21:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 11:27 [9fans] plan 9 wiki experiment Russ Cox
2001-02-01 8:08 ` Quinn Dunkan
2001-02-01 8:01 ` Dan Cross
[not found] ` <cross@math.psu.edu>
2001-02-01 19:38 ` Tom Duff
2001-02-05 18:55 ` Dan Cross
2001-02-14 21:43 ` Mark C. Otto [this message]
2001-02-14 21:57 ` [9fans] KFS Crash Scott Schwartz
2001-02-27 14:08 ` [9fans] PS2 vs Com1 Mouse Problems Mark C. Otto
2001-02-27 15:48 ` Mark C. Otto
2001-02-14 22:01 [9fans] KFS Crash Russ Cox
2001-02-15 14:31 ` Mark C. Otto
2001-02-14 22:02 Russ Cox
2001-02-14 23:06 rob pike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A8AFBFB.2890AF90@FWS.Gov \
--to=mark_otto@fws.gov \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).