From: hugo rivera <uair00@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] venti question
Date: Wed, 13 May 2009 10:51:11 +0200 [thread overview]
Message-ID: <138575260905130151r2b0f58d9p515332a7a47825a5@mail.gmail.com> (raw)
In-Reply-To: <b29170d0adb7f667dace79a543cbcb3d@quintile.net>
I am trying to use buildindex but I run into trouble:
1.- the man page and the usage displayed by the command are
inconsistent. According to the man page, buildindex takes two
arguments and may take two options
venti/buildindex [ -B blockcachesize ] [ -Z ] venti.conf tmp
but execute buildindex with no arguments and you get
usage: buildindex [-bd] [-i isect]... [-M imem] venti.conf
options -b -d -i -M are not described in the man page and I have no
idea what they are supposed to do (although I can imagine the use of
-i and -b), and there's no tmp file required anymore.
2. I edited my venti.conf, so now it looks like
index main
isect /apollo/hugo/isect0
isect /apollo/hugo/isect1 # --> new line, not found in the
original venti.conf
arenas /apollo/hugo/arenas0
arenas /apollo/hugo/arenas1 # --> new line, not found in the
original venti.conf
but when I ran
venti/buildindex -i isect1 $home/lib/venti.conf
I got
err 2: mismatched number index sections: found 2 expected 1
venti/buildindex: can't init venti: mismatched number index sections:
found 2 expected 1
so I removed the isect1 line from my venti.conf and executed
venti/buildindex -i isect1 $home/lib/venti.conf
and got
1,731,717 clumps, 63,903 buckets
2009/0513 10:35:35 read index
warning: did not find index section isect1
2009/0513 10:35:35 arena arenas00: 236950 entries
2009/0513 10:35:36 arena arenas01: 317534 entries
2009/0513 10:35:36 arena arenas02: 69564 entries
2009/0513 10:35:36 arena arenas03: 231390 entries
2009/0513 10:35:37 arena arenas04: 246845 entries
2009/0513 10:35:37 arena arenas05: 65202 entries
2009/0513 10:35:38 arena arenas06: 65204 entries
2009/0513 10:35:38 arena arenas07: 77445 entries
2009/0513 10:35:38 arena arenas08: 65197 entries
2009/0513 10:35:38 arena arenas09: 65189 entries
2009/0513 10:35:38 arena arenas010: 126699 entries
2009/0513 10:35:39 arena arenas011: 137570 entries
2009/0513 10:35:39 arena arenas012: 26928 entries
2009/0513 10:35:39 done arenaentries=1,731,717 indexed=0 (nskip=0)
which complains about not finding isect1, so I am quite confused now.
I also tried some other combinations, but I always got the "mismatched
number of index sections" error. I saw Steve's article, but he uses
the syntax described in the man page which, if given to my buildindex
version, produces the usage output on screen. Note that I am using
p9p.
Any help appreciated.
--
Hugo
next prev parent reply other threads:[~2009-05-13 8:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 13:20 hugo rivera
2009-05-12 15:17 ` Latchesar Ionkov
2009-05-12 15:29 ` hugo rivera
2009-05-12 15:43 ` erik quanstrom
2009-05-12 16:35 ` Steve Simon
2009-05-13 8:51 ` hugo rivera [this message]
2009-05-13 11:47 ` erik quanstrom
2009-05-13 12:41 ` hugo rivera
2009-05-13 11:49 ` Steve Simon
2009-05-13 13:34 ` hugo rivera
-- strict thread matches above, loose matches on Subject: below --
2004-08-12 23:27 [9fans] xen port ron minnich
2004-08-17 0:40 ` [9fans] venti question Tim Newsham
2004-08-17 15:40 ` Russ Cox
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=138575260905130151r2b0f58d9p515332a7a47825a5@mail.gmail.com \
--to=uair00@gmail.com \
--cc=9fans@9fans.net \
/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).