From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] KFS Crash
Date: Wed, 14 Feb 2001 16:57:31 -0500 [thread overview]
Message-ID: <20010214215731.15953.qmail@g.bio.cse.psu.edu> (raw)
In-Reply-To: Message from "Mark C. Otto" <Mark_Otto@FWS.Gov> of "Wed, 14 Feb 2001 16:43:23 EST." <3A8AFBFB.2890AF90@FWS.Gov>
> Would you like to ream it (y/n)? tag = <badtag>;Tdir
It's kinda bad that it doesn't give you a chance to answer the question.
A kfs on a rescue floppy would at least let you check the filesystem
and maybe recover something.
next prev parent reply other threads:[~2001-02-14 21:57 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 ` [9fans] KFS Crash Mark C. Otto
2001-02-14 21:57 ` Scott Schwartz [this message]
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=20010214215731.15953.qmail@g.bio.cse.psu.edu \
--to=schwartz@bio.cse.psu.edu \
--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).