From: Matthias Bauer <bauerm@pestilenz.org>, Matthias Bauer <plan9@weggla.franken.de>
To: 9fans@cse.psu.edu
Cc: christian.kellermann@nefkom.net
Subject: [9fans] venti p9p problems
Date: Sun, 1 Oct 2006 02:38:54 +0200 [thread overview]
Message-ID: <20061001003854.GA22525@pestilenz.org> (raw)
Hi 9fans,
While playing with p9p venti and vac I came about
the following problem:
The venti server is running on OpenBSD 4.0.
I stored a directory (about 115Mb) in venti with vac. The debugging
output told that it stored all the files on the
server. After transferring the vacfile to a plan9 host,
I tried to access the stored directory with vacfs vacfile.
Unfortunately the /n/vac/ dir only contains the dot .
C-Keen and I retried several times on different machines, slightly
different venti setups (arenas, isects) and with
lots of debugging options, but could not get at
the data.
Below is the log of the last vacfs try (for vac:7c59cdd58e2ea5d654c74f1eea25caea91071c31)
as returned by the venti-http.
Thanks,
Matthias
------
work ventiserver: start request Tread tag 0 score 7c59cdd58e2ea5d654c74f1eea25caea91071c31 blocktype 16 count 300
rpc ventiserver: <- Tread tag 0 score 7c59cdd58e2ea5d654c74f1eea25caea91071c31 blocktype 16 count 300
lump ventiserver: readlump enter
lump ventiserver: lookuplump enter
lump ventiserver: lookuplump hit
lump ventiserver: lookuplump exit
lump ventiserver: readlump lookuplump hit
lump ventiserver: putlump
lump ventiserver: putlump wakeup
rpc ventiserver: -> Rread tag 0 count 300
work ventiserver: start
work ventiserver: finish
work ventiserver: start request Tread tag 0 score 1566fc8077e44a034f804b302a57968b79a6040f blocktype 8 count 8192
rpc ventiserver: <- Tread tag 0 score 1566fc8077e44a034f804b302a57968b79a6040f blocktype 8 count 8192
lump ventiserver: readlump enter
lump ventiserver: lookuplump enter
lump ventiserver: lookuplump hit
lump ventiserver: lookuplump exit
lump ventiserver: readlump lookuplump hit
lump ventiserver: putlump
lump ventiserver: putlump wakeup
rpc ventiserver: -> Rread tag 0 count 120
work ventiserver: start
work ventiserver: finish
work ventiserver: start request Tread tag 0 score 73999d40ad65f71b598eb5d1f6c7793f6a56e11d blocktype 0 count 8192
rpc ventiserver: <- Tread tag 0 score 73999d40ad65f71b598eb5d1f6c7793f6a56e11d blocktype 0 count 8192
lump ventiserver: readlump enter
lump ventiserver: lookuplump enter
lump ventiserver: lookuplump hit
lump ventiserver: lookuplump exit
lump ventiserver: readlump lookuplump hit
lump ventiserver: putlump
lump ventiserver: putlump wakeup
rpc ventiserver: -> Rread tag 0 count 412
work ventiserver: start
proc delaykickproc dcache: kickround 0xc
proc delaykickproc dcache: kick dcache
work flushproc: start
proc flushproc: build t=1
proc flushproc: writeblocks t=31
proc flushproc: writeblocks.1 t=55
proc flushproc: writeblocks.2 t=79
proc flushproc: writeblocks.3 t=103
proc flushproc: undirty.4 t=127
work flushproc: finish
proc delaykickproc dcache: finishround 0xc
proc delaykickproc dcache: waitround 0xd
work ventiserver: finish
work ventiserver: start request Tread tag 0 score e1f18bbaa8e1378bd816f008648d579a7aeac895 blocktype 0 count 8192
rpc ventiserver: <- Tread tag 0 score e1f18bbaa8e1378bd816f008648d579a7aeac895 blocktype 0 count 8192
lump ventiserver: readlump enter
lump ventiserver: lookuplump enter
lump ventiserver: lookuplump hit
lump ventiserver: lookuplump exit
lump ventiserver: readlump lookuplump hit
lump ventiserver: putlump
lump ventiserver: putlump wakeup
rpc ventiserver: -> Rread tag 0 count 406
work ventiserver: start
next reply other threads:[~2006-10-01 0:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 0:38 Matthias Bauer, Matthias Bauer [this message]
2006-10-01 13:41 ` Russ Cox
2006-10-01 14:58 ` Matthias Bauer
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=20061001003854.GA22525@pestilenz.org \
--to=bauerm@pestilenz.org \
--cc=9fans@cse.psu.edu \
--cc=christian.kellermann@nefkom.net \
--cc=plan9@weggla.franken.de \
/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).