* [sup-talk] Crash while indexing 47000 message maildir
@ 2007-10-13 5:00 Brandon Philips
2007-10-30 20:41 ` William Morgan
0 siblings, 1 reply; 2+ messages in thread
From: Brandon Philips @ 2007-10-13 5:00 UTC (permalink / 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
^ permalink raw reply [flat|nested] 2+ messages in thread
* [sup-talk] Crash while indexing 47000 message maildir
2007-10-13 5:00 [sup-talk] Crash while indexing 47000 message maildir Brandon Philips
@ 2007-10-30 20:41 ` William Morgan
0 siblings, 0 replies; 2+ messages in thread
From: William Morgan @ 2007-10-30 20:41 UTC (permalink / raw)
Excerpts from Brandon Philips's message of Fri Oct 12 22:00:48 -0700 2007:
> I got the following error after I started sup-add on 47118 message
> maildir and tried to view the label while sup was indexing.
Simultaneous index access breaks Ferret in weird ways. Sup 0.2 locks the
index to avoid this.
--
William <wmorgan-sup at masanjin.net>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-10-30 20:41 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-10-13 5:00 [sup-talk] Crash while indexing 47000 message maildir Brandon Philips
2007-10-30 20:41 ` William Morgan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox