From: "david bulkow" <dbulkow@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] migrating from oventi to nventi
Date: Mon, 3 Mar 2008 15:11:21 -0500 [thread overview]
Message-ID: <2d5a784f0803031211x2eee97f4x9791d7471c0073df@mail.gmail.com> (raw)
In-Reply-To: <ce0d142f909b265d35608dc552fe30c7@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
On Mon, Mar 3, 2008 at 3:26 PM, <cinap_lenrek@gmx.de> wrote:
> 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.
[-- Attachment #2: Type: text/html, Size: 814 bytes --]
next prev parent reply other threads:[~2008-03-03 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 20:26 cinap_lenrek
2008-03-03 20:11 ` david bulkow [this message]
2008-03-03 21:58 ` cinap_lenrek
2008-03-05 9:24 ` [9fans] migrating from oventi to nventi *solved* Kernel Panic
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=2d5a784f0803031211x2eee97f4x9791d7471c0073df@mail.gmail.com \
--to=dbulkow@gmail.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).