Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sup not working anymore after abrupt reboot
Date: Fri, 13 Nov 2009 13:10:17 +0200	[thread overview]
Message-ID: <1258109288-sup-5579@tilus.net> (raw)
In-Reply-To: <21063fcb0911130111h234098b5oabe77bfdd14a0dab@mail.gmail.com>

Carlos Garcia Campos, 2009-11-13 11:11:
> I don't know whether my ferret index is corrupt, this is the exception  I
> get:
> 
> ----------------------------------------------------------------
> Error occured in index.c:901 - sis_find_segments_file
> Error reading the segment infos.

I'm not familiar with the internals of ferret, but the error looks
pretty bad.  It might have lost part of index data files.  Do you
happen to have index or dump backups or find deleted files under
ferret/ with using undelete tools?

Lessons learned...

Always have regular (automatic, if possible) backups of your index
dump, ALWAYS!  I have sup-dump in my backup2l before-hook.

Hum.  I think for people who don't do cron backups it wouldn't be a
bad idea to create (optional) rotating sup-dumps on every start. (and
stop?)

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2009-11-13 11:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13  9:11 Carlos Garcia Campos
2009-11-13 11:10 ` Tero Tilus [this message]
2009-11-14 13:22   ` Carlos Garcia Campos
2009-11-13 11:57 ` Gaute Hope

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=1258109288-sup-5579@tilus.net \
    --to=tero@tilus.net \
    --cc=sup-talk@rubyforge.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