Re: [9fans] p9p vac issue

["Mathieu L." <lejatorn@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 492 bytes --]

Indeed, this works for me as well.
I've just migrated the arenas, bloom and isect to another machine with
a p9p tree from mid February and I had no problem unvacing my data
there. And for what it's worth, checkindex on that machine didn't report
any problem while it did on the machine with the recent p9p install
(which gives me the same vac/unvac issues as the ones already reported
by a few people).
So the data seems to be ok, which is already quite a relief.

Cheers,
Mathieu

[-- Attachment #2: Type: message/rfc822, Size: 4326 bytes --]

From: phætøn <phaet0n@hotmail.com>
To: <9fans@9fans.net>
Subject: [9fans] p9p vac issue
Date: Mon, 22 Jun 2009 04:10:56 -0400
Message-ID: <BLU139-W204D6ABA8273A9199C91C9F9390@phx.gbl>


X-No-Archive: Yes

 
This is not much of a solution to the problem,

however I have temporarily resolved my issue

by performing vac/unvac using my p9p tree

from mid-March, and then resorting to the

latest p9p for vacfs/9pfuse in order to mount

my archives.

 
For those researching the issue, I think some

change between the middle of March and now

is causing the inability of vac to write to a

venti archive on p9p with the error:
 
create bsize 8192 psize 8160vac: vacfscreate: vacfileroot: read too small: asked for 0 need at least 389



_________________________________________________________________
Windows Live helps you keep up with all your friends, in one place.
http://go.microsoft.com/?linkid=9660826