From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Can't even run sup anymore
Date: Sat, 21 Jun 2008 19:36:18 -0700 [thread overview]
Message-ID: <1214101954-sup-8941@entry> (raw)
In-Reply-To: <1e5fdab70806211505p5146fd10le45d8853ec5ca31c@mail.gmail.com>
Reformatted excerpts from guillaume.quintard's message of 2008-06-21:
> IO Error occured at <except.c>:93 in xraise
> Error occured in index.c:901 - sis_find_segments_file
> Error reading the segment infos. Store listing was
This is the classic Sup+ferret error. No one really knows what the heck
is going on, although there's a guess it has to do with open files:
http://ferret.davebalmain.com/trac/ticket/279
I've had success before with sup-sync --optimize. You can try that.
Otherwise, it's rebuild the index and bug Dave Balmain...
I am working on something where flags are backed up to a BDB store on
disk, which is yet more disk space consumed by Su, but at least means
that if Ferret barfs you don't lose all your message flags. Of course,
that doesn't help you right now.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-06-22 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 22:05 Guillaume Quintard
2008-06-22 2:36 ` William Morgan [this message]
2008-06-22 18:16 ` Guillaume Quintard
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=1214101954-sup-8941@entry \
--to=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