From: Steven Walter <stevenrwalter@gmail.com>
To: William Morgan <wmorgan-sup@masanjin.net>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Recovering a busted ferret db?
Date: Fri, 30 Oct 2009 18:14:32 -0400 [thread overview]
Message-ID: <e06498070910301514ud4efe49ic0fb40d181156fab@mail.gmail.com> (raw)
In-Reply-To: <1256939095-sup-4201@masanjin.net>
On Fri, Oct 30, 2009 at 5:48 PM, William Morgan
<wmorgan-sup@masanjin.net> wrote:
> Reformatted excerpts from Steven Walter's message of 2009-10-30:
>> I think my ferret db is corrupted. Whenever I do a tag search for a
>> specific tag, sup loads 2 messages and then hangs. Actually, it's
>> using 100% CPU, but I have to kill -9 it; ctrl-c doesn't work. Is
>> there any hope of fixing this without losing all my tag information?
>
> You can certainly move to the Xapian index without losing all of your
> tags. Sup-dump will output everything precious from your index.
Looks like sup-dump hangs, too.
> Is it possible you have a very large thread with that label? E.g.
> thousands of messages, all replying to each other, from some script?
Not very likely. I could believe tens, up to a hundred; 200 at the most.
I am able to Ctrl-C sup-dump when it hangs. Here's the ruby backtrace:
/var/lib/gems/1.8/gems/sup-0.9/lib/sup/util.rb:206:in `split': Interrupt
from /var/lib/gems/1.8/gems/sup-0.9/lib/sup/util.rb:206:in
`split_on_commas'
from /var/lib/gems/1.8/gems/sup-0.9/lib/sup/person.rb:108:in
`from_address_list'
from /var/lib/gems/1.8/gems/sup-0.9/lib/sup/message.rb:104:in
`parse_header'
from /var/lib/gems/1.8/gems/sup-0.9/lib/sup/ferret_index.rb:276:in
`build_message'
from /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
from /var/lib/gems/1.8/gems/sup-0.9/lib/sup/ferret_index.rb:256:in
`build_message'
from /var/lib/gems/1.8/gems/sup-0.9/lib/sup/index.rb:150:in
`each_message'
from /var/lib/gems/1.8/gems/sup-0.9/lib/sup/ferret_index.rb:319:in
`each_id'
from /var/lib/gems/1.8/gems/sup-0.9/lib/sup/ferret_index.rb:319:in `map'
from /var/lib/gems/1.8/gems/sup-0.9/lib/sup/ferret_index.rb:319:in
`each_id'
from /var/lib/gems/1.8/gems/sup-0.9/lib/sup/index.rb:149:in
`each_message'
from /var/lib/gems/1.8/gems/sup-0.9/bin/sup-dump:28
--
-Steven Walter <stevenrwalter@gmail.com>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-10-30 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 17:17 Steven Walter
2009-10-30 21:48 ` William Morgan
2009-10-30 22:14 ` Steven Walter [this message]
2009-11-01 14:53 ` William Morgan
[not found] ` <e06498070911011203s66ece542mac80378442073369@mail.gmail.com>
2009-11-02 11:53 ` William Morgan
2009-11-02 12:35 ` William Morgan
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=e06498070910301514ud4efe49ic0fb40d181156fab@mail.gmail.com \
--to=stevenrwalter@gmail.com \
--cc=sup-talk@rubyforge.org \
--cc=wmorgan-sup@masanjin.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