From: Kernel Panic <cinap_lenrek@gmx.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] migrating from oventi to nventi *solved*
Date: Wed, 5 Mar 2008 10:24:27 +0100 [thread overview]
Message-ID: <47CE66CB.5030309@gmx.de> (raw)
In-Reply-To: <649470b12b8833555f7a29a2ed097cc7@gmx.de>
>>first tried to extract arenas with oventis venti/rdarena and then
>>pumping them into nventi with nventis venti/wrarena.
>>when tried to format fossil with the last root-score, it failed to
>>find the block.
>>
>>
>I have found the need to rebuild the index a couple of times with nventi
>since i switched from old to new. The first was just after switching
>in-place from old to new. The second was a month later when I started to
>see block-rot again, although most likely caused by something I did.
>
>
good hint, works for me!
pulled/pushed arenas with oventi venti/rdarena venti/wrarena and after
all arenas where
copied, it rebuild the index with nventis venti/buildindex (btw.
buildindex doesnt require
a temporary space anymore, so thanks to the author for this improvement).
thanks again! :-)
cinap
prev parent reply other threads:[~2008-03-05 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 20:26 [9fans] migrating from oventi to nventi cinap_lenrek
2008-03-03 20:11 ` david bulkow
2008-03-03 21:58 ` cinap_lenrek
2008-03-05 9:24 ` Kernel Panic [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=47CE66CB.5030309@gmx.de \
--to=cinap_lenrek@gmx.de \
--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).