From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cs.psu.edu
Subject: [9fans] venti/checkarenas
Date: Fri, 10 Sep 2004 09:29:49 +0100 [thread overview]
Message-ID: <18ce19a4c9788397e5576b3c188e5a7e@terzarima.net> (raw)
i find that the last batch of changes written to venti always
yields diagnostics like the following from subsequent venti/checkarenas:
unwritten clump info for clump=78327 score=096aebf110967672346d6b22597aaf28bb070a61 type=2
unwritten clump info for clump=78328 score=78b812a6153d4ba818625767c63d177878247390 type=13
unwritten clump info for clump=78329 score=2f5755c62e26aacb9ef323998c346ea4d4f22f79 type=2
unwritten clump info for clump=78330 score=d46c5390d95cfb6a58fdd9fa72ac705626a8d151 type=13
unwritten clump info for clump=78331 score=1e21e26ee81d03f4df808dad975a465e73a15a5e type=13
unwritten clump info for clump=78332 score=5f818cf12419acdb6498d05b6ecc849e78562263 type=2
unwritten clump info for clump=78333 score=92e25ecb6c7ad80415cf8cc1916eb001c7b0dea2 type=2
unwritten clump info for clump=78334 score=332e3a8eef00a8ccbb307b143757b33f3fcb72d2 type=1
incorrect arena header fields
...
venti/sync doesn't change the result.
when i'd changed venti/checkarenas -f to repair them correctly (rather,
remember that it had repaired them) i'd assumed that i'd shut down at
some point before it could write the clump info. it's so consistent on
several venti, though, that i now assume i've misinterpreted.
mind you, one time i couldn't use the result until i'd done the checkarenas -f
and rebuilt the index. any comments?
next reply other threads:[~2004-09-10 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 8:29 Charles Forsyth [this message]
2004-09-09 14:38 ` jmk
2004-09-09 17:04 ` 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=18ce19a4c9788397e5576b3c188e5a7e@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cs.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).