From: Rich Lane <rlane@club.cc.cmu.edu>
To: Guillaume Quintard <guillaume.quintard@gmail.com>
Cc: "Sup-talk@rubyforge.org" <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Crash, bad index, and ensuing misery
Date: Sat, 03 Oct 2009 16:17:54 -0400 [thread overview]
Message-ID: <1254600926-sup-5190@zyrg.net> (raw)
In-Reply-To: <1e5fdab70910031304g255a9d13v4dc99400def375a5@mail.gmail.com>
Excerpts from Guillaume Quintard's message of Sat Oct 03 16:04:14 -0400 2009:
> Hi, I crash my computer with sup running, and it seems the index
> didn't really like. sup-sync -a didn't help, what can I do?
I'd hoped this kind of corruption wouldn't be possible with newer
xapian-index versions. What sup commit are you on? What version of
Xapian are you using? Which Xapian backend, Flint or Chert?
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-10-03 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 20:04 Guillaume Quintard
2009-10-03 20:17 ` Rich Lane [this message]
2009-10-03 21:06 ` Guillaume Quintard
2009-10-03 21:39 ` Rich Lane
2009-10-03 21:54 ` Guillaume Quintard
2009-10-06 12:40 ` Olly Betts
2009-10-06 13:10 ` Guillaume Quintard
2009-10-03 22:25 ` Rich Lane
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=1254600926-sup-5190@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=guillaume.quintard@gmail.com \
--cc=sup-talk@rubyforge.org \
/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