From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] file server trouble
Date: Tue, 2 Apr 2002 21:57:38 +0100 [thread overview]
Message-ID: <20020402205607.A7F1119A27@mail.cse.psu.edu> (raw)
i'd try recover main in config mode. for whatever reason, some blocks
were not written out. alternatively, they were, but the fworm bitmap blocks
weren't, and if they aren't right, you still can't read the data blocks.
in some cases, you might need to build a kernel to allow you to go further
back than `recover main' (with a pseudo-worm), but i've not actually had to do that.
next reply other threads:[~2002-04-02 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 20:57 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-03 20:28 forsyth
2002-04-03 20:08 anothy
2002-04-03 16:56 forsyth
2002-04-03 16:39 anothy
2002-04-02 23:18 Geoff Collyer
2002-04-02 23:06 Geoff Collyer
2002-04-02 22:10 anothy
2002-04-02 20:36 anothy
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=20020402205607.A7F1119A27@mail.cse.psu.edu \
--to=forsyth@vitanuova.com \
--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).