From: "Mathieu L." <lejatorn@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] p9p vac issue
Date: Mon, 22 Jun 2009 14:08:28 +0200 [thread overview]
Message-ID: <76be69f155cec68df27d6bc6bc2950ea@smgl.fr.eu.org> (raw)
In-Reply-To: <166806220906220433ya10a40fy7ee67cfb78f28c5@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 170 bytes --]
if you can't get an old one from swtch.com, I can tar this mid-february
tree I have - or rather only the necessary parts - and serve it to you
if you want.
Mathieu
[-- Attachment #2: Type: message/rfc822, Size: 7104 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 761 bytes --]
2009/6/22 Mathieu L. <lejatorn@gmail.com>
> 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).
OK, so all I need now is to get my hands on an old copy of the p9p
binaries... the only old ones I've got are carefully backed up inside the
venti that I can't get at :)
> So the data seems to be ok, which is already quite a relief.
>
> Cheers,
> Mathieu
--
Adrian
[-- Attachment #2.1.2: Type: text/html, Size: 1389 bytes --]
next prev parent reply other threads:[~2009-06-22 12:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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. [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2009-06-21 4:18 phætøn
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=76be69f155cec68df27d6bc6bc2950ea@smgl.fr.eu.org \
--to=lejatorn@gmail.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).