From: Dave Eckhardt <davide+p9@cs.cmu.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] 423 missing clumps
Date: Tue, 5 Jul 2005 15:22:32 -0400 [thread overview]
Message-ID: <10526.1120591352@piper.nectar.cs.cmu.edu> (raw)
I have an old venti (/bin/venti/venti is dated November 2003) whose
bits I would like to transfer elsewhere as part of an upgrade.
Because I'm paranoid I checked the venti index information available
from http://127.1:8000/index against the output of rdarena and was
disturbed to find that rdarena was seeing 423 fewer clumps than
venti knew about. I tried venti/sync (followed by waiting) and
also issuing "venti" on the fossil console to hang up and redial
its connection, all to no avail.
Then I read about the "clump info not on disk" issue discussed
in <http://lists.cse.psu.edu/archives/9fans/2004-September/037962.html>.
Sure enough, rebooting my fossi/venti machine caused the "missing"
clumps to be visible to rdarena.
Has venti been changed so that venti/sync forces the clump information
out to disk? Should a warning be added to the ventiaux manual
page, at least for people running old code?
Dave Eckhardt
reply other threads:[~2005-07-05 19:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=10526.1120591352@piper.nectar.cs.cmu.edu \
--to=davide+p9@cs.cmu.edu \
--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).