From: Venkatesh Srinivas <me@acm.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Possible bug in p9p venti?
Date: Tue, 25 Aug 2009 22:10:12 -0400 [thread overview]
Message-ID: <f75780240908251910m5cdd26cch814f6934ad2e4600@mail.gmail.com> (raw)
In-Reply-To: <0fb4b173c97af1d352581fdf264afca7@quanstro.net>
On Tue, Aug 25, 2009 at 8:08 PM, erik quanstrom<quanstro@quanstro.net> wrote:
>>
>> Any chance this is related to the issues we discussed on #plan9?
>>
No, I'm pretty sure not. This dealt with a relatively rare case, a
filesystem with an optimal read size larger than a constant in the
Venti source. The constant was 64K, which covered every FS/OS cross I
know of except ZFS on FreeBSD.
>
> since not everyone who reads the list does irc, why
> don't you fill us in on the issues discussed on #plan9?
>
The problem discussed in IRC relates to p9p vac's -a option, which
chains together vac trees to construct something like a dump
filesystem on unix.
The first problem was that a vac -a hadn't be run in a while, and the
newly added tree has some problem with it (either stored incorrectly
or being interpreted incorrectly...), which led to it being impossible
to traverse or base further vacs on.
The person in irc also had a problem where they blew away their Venti
index, rebuilt the index, and had checkindex still report errors. That
problem is pretty exciting too...
-- vs
next prev parent reply other threads:[~2009-08-26 2:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 15:10 Venkatesh Srinivas
2009-08-23 16:23 ` Russ Cox
2009-08-26 0:04 ` J.R. Mauro
2009-08-26 0:08 ` erik quanstrom
2009-08-26 2:10 ` Venkatesh Srinivas [this message]
2009-08-26 16:14 ` J.R. Mauro
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=f75780240908251910m5cdd26cch814f6934ad2e4600@mail.gmail.com \
--to=me@acm.jhu.edu \
--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).