From: brandon@ifup.org (Brandon Philips)
Subject: [sup-talk] Crash while indexing 47000 message maildir
Date: Fri, 12 Oct 2007 22:00:48 -0700 [thread overview]
Message-ID: <20071013050048.GA16465@ifup.org> (raw)
Hello-
I got the following error after I started sup-add on 47118 message
maildir and tried to view the label while sup was indexing.
sup-add maildir:/home/philips/Mail/ifup.linux-kernel/ -a -l lkml
sup
L lkml <enter>
Crash.
Thanks,
Brandon
/var/lib/gems/1.8/gems/sup-0.1/lib/sup/buffer.rb:32: warning: already
initialized constant KEY_ENTER
/var/lib/gems/1.8/gems/sup-0.1/lib/sup/buffer.rb:33: warning: already
initialized constant KEY_CANCEL
[Fri Oct 12 21:51:14 -0700 2007] locking /home/philips/.sup/lock...
[Fri Oct 12 21:51:14 -0700 2007] loading index...
[Fri Oct 12 21:51:14 -0700 2007] loaded index of 5017 messages
[Fri Oct 12 21:51:14 -0700 2007] starting curses
[Fri Oct 12 21:56:02 -0700 2007] stopped cursing
[Fri Oct 12 21:56:02 -0700 2007] oh crap, an exception
[Fri Oct 12 21:56:02 -0700 2007] unlocking /home/philips/.sup/lock...
----------------------------------------------------------------
I'm very sorry, but it seems that an error occurred in Sup.
Please accept my sincere apologies. If you don't mind, please
send the backtrace below and a brief report of the circumstances
to sup-talk at rubyforge dot orgs so that I might address this
problem. Thank you!
Sincerely,
William
----------------------------------------------------------------
The problem was: 'IO Error occured at <except.c>:93 in xraise
Error occured in fs_store.c:293 - fsi_seek_i
seeking pos 29850024: <Bad file descriptor>
' (error type IOError)
A backtrace follows:
/var/lib/gems/1.8/gems/sup-0.1/lib/sup/index.rb:300:in `default': IO
Error occured at <except.c>:93 in xraise (IOError)
Error occured in fs_store.c:293 - fsi_seek_i
seeking pos 29850024: <Bad file descriptor>
from /var/lib/gems/1.8/gems/sup-0.1/lib/sup/index.rb:300:in `[]'
from /var/lib/gems/1.8/gems/sup-0.1/lib/sup/index.rb:300:in
`build_message'
from /var/lib/gems/1.8/gems/sup-0.1/lib/sup/index.rb:274:in
`each_message_in_thread_for'
from /var/lib/gems/1.8/gems/sup-0.1/lib/sup/thread.rb:316:in
`call'
from /var/lib/gems/1.8/gems/sup-0.1/lib/sup/thread.rb:316:in
`load_thread_for_message'
from /var/lib/gems/1.8/gems/sup-0.1/lib/sup/index.rb:281:in
`each_message_in_thread_for'
from /var/lib/gems/1.8/gems/sup-0.1/lib/sup/index.rb:281:in
`each'
from /var/lib/gems/1.8/gems/sup-0.1/lib/sup/index.rb:281:in
`each_message_in_thread_for'
... 16 levels...
from
/var/lib/gems/1.8/gems/sup-0.1/lib/sup/modes/thread-index-mode.rb:394:in
`load_threads'
from /var/lib/gems/1.8/gems/sup-0.1/bin/sup:233
from /var/lib/gems/1.8/bin/sup:16:in `load'
from /var/lib/gems/1.8/bin/sup:16
next reply other threads:[~2007-10-13 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 5:00 Brandon Philips [this message]
2007-10-30 20:41 ` 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=20071013050048.GA16465@ifup.org \
--to=brandon@ifup.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