From: phætøn <phaet0n@hotmail.com>
To: <9fans@9fans.net>
Subject: [9fans] p9p vac issue
Date: Sun, 21 Jun 2009 00:18:21 -0400 [thread overview]
Message-ID: <BLU139-W35B96D86892F2CA5D8D11DF9380@phx.gbl> (raw)
X-No-Archive: Yes
Adrian T. wrote:> There were a few followups with a subject of> "p9p venti problem", but no fix.
I had looked up that thread, and the thread that Venkatesh S.refers to earlier with the subject "P9P venti/copy bug?" from9fans:2009/02:198. Nathaniel F. suggests a patch in 9fans:2009/03:730 however that doesn't solve the problem for me.I had looked through the hg history for p9p and the patchwas never merged, so I'd manually applied it and rebuilt tono avail.
I am not really familiar with the structure of vac or venti. Ido have a large archive on an external drive, and encounteredthis problem when attempting to see how file structure wasexposed with embedded .vac files in the archive tree. I canstill read my old archive, however I am weary of addingdata to it without some resolution to this issue for fear ofcorrupting what is already there.
I too would like to see a resolution to this long standing issue.
_________________________________________________________________
Windows Live helps you keep up with all your friends, in one place.
http://go.microsoft.com/?linkid=9660826
next reply other threads:[~2009-06-21 4:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 4:18 phætøn [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-22 8:10 phætøn
2009-06-22 8:33 ` Mathieu L.
2009-06-22 11:33 ` Adrian Tritschler
2009-06-22 12:06 ` Josh Wood
2009-06-22 12:08 ` Mathieu L.
2009-06-22 14:40 ` Fernan Bolando
2009-06-22 16:20 ` Fernan Bolando
2009-06-22 16:50 ` erik quanstrom
[not found] ` <d7c5dc2d2043edb5f99143a8e701f5e8@quanstro.net>
2009-06-27 2:12 ` Fernan Bolando
2009-06-20 16:11 phætøn
2009-06-21 0:08 ` Adrian Tritschler
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=BLU139-W35B96D86892F2CA5D8D11DF9380@phx.gbl \
--to=phaet0n@hotmail.com \
--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).