Subject: [sup-talk] Crash while indexing 47000 message maildir

From: [email-masked] (Brandon Philips)
Date: Fri, 12 Oct 2007 22:00:48 -0700

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

---

From: [email-masked] (William Morgan)
Date: Tue, 30 Oct 2007 13:41:48 -0700

> 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>