From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] venti back anyway
Date: Thu, 5 Feb 2004 09:30:10 -0500 [thread overview]
Message-ID: <838c67043dd22cc22d1e08e4559ecd81@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0402042352050.32456-100000@maxroach.lanl.gov>
On Thu Feb 5 02:02:24 EST 2004, rminnich@lanl.gov wrote:
> ...
> I get back three lines of hex numbers, no errors. Are three lines of hex
> numbers pretty much the thing to expect?
> ...
yes, those are the scores of the 3 entries in the root.
if you didn'y get any other errors you're ok.
> ...
> But if I try to start fossil, well, that goes badly. The first line of
> config is this:
> fsys main config /dev/sdC0/isect1
> and that gets this error:
> fsOpen: fileRoot: i/o error
> ...
can you mount the archive you have the score for, e.g.
vacfs -h venti-server vac-file-with-root-score
prev parent reply other threads:[~2004-02-05 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 7:01 ron minnich
2004-02-05 14:30 ` jmk [this message]
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=838c67043dd22cc22d1e08e4559ecd81@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.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).