From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil/flfmt -v problem
Date: Thu, 3 Jul 2003 23:23:42 -0400 [thread overview]
Message-ID: <a945610a734d95afe9c521aba44dc613@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0307031643230.18814-100000@fbsd.cpsc.ucalgary.ca>
On Thu Jul 3 18:51:22 EDT 2003, mirtchov@cpsc.ucalgary.ca wrote:
> [ very long story short, i'm trying to recover from couple days ago's venti,
> using a score i got doing 'main: vac /archive/2003/0701' ]
>
> here's the problem:
>
>
> # fossil/flfmt -v e24ddc5eaea97b3ad947c9d5a3b5a796c548249b /dev/sdD0/fossil
> fs header block already exists; are you sure? [y/n]: y
> 48cbf63405e14adef602c44fd7e14cd6b5471793
> 0c273af08c6045a9ddc58840622453929e06c206
> e457e4fdd6fb49bf7d4b932568aa964adc139ce1
> fatal error: bad root: no qidSpace
> #
>
Flfmt needs a score created by an archive snapshot, not a vac file
(as I understand it).
It's funny, I was working on making this work (i.e. using a vac score
to initialise a filesystem) earlier in the week and 'sort of' have it
working, but there are details needing to be done that I won't get to
for a while. The particular detail you are sticking over here is that
the max qid used in the vac file is held in a different place in a 'real'
vac file (qid entry of the root directory entry) than in an archive
snapshot (root metadata qidspace entry).
next prev parent reply other threads:[~2003-07-04 3:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 22:50 andrey mirtchovski
2003-07-04 3:23 ` jmk [this message]
2003-07-04 3:35 ` andrey mirtchovski
2003-07-04 3:57 ` jmk
2003-07-04 4:37 ` andrey mirtchovski
2003-07-04 13:37 ` Fco.J.Ballesteros, nemo
2003-07-04 13:51 ` andrey mirtchovski
2003-07-04 16:42 ` jmk
2003-07-04 17:17 ` Fco.J.Ballesteros, nemo
2003-07-04 17:21 ` rog
2003-07-04 17:20 ` Fco.J.Ballesteros, nemo
2003-07-04 17:25 ` Fco.J.Ballesteros, nemo
2003-07-04 17:46 ` rog
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=a945610a734d95afe9c521aba44dc613@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).