From: Carlos Garcia Campos <carlosgc@gnome.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sup not working anymore after abrupt reboot
Date: Sat, 14 Nov 2009 14:22:50 +0100 [thread overview]
Message-ID: <1258204741-sup-4254@charmaleon> (raw)
In-Reply-To: <1258109288-sup-5579@tilus.net>
[-- Attachment #1.1: Type: text/plain, Size: 1147 bytes --]
Excerpts from Tero Tilus's message of vie nov 13 12:10:17 +0100 2009:
> 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.
indeed, I have had to build a new index scratch.
> Do you
> happen to have index or dump backups or find deleted files under
> ferret/ with using undelete tools?
No :-/
> Lessons learned...
>
> Always have regular (automatic, if possible) backups of your index
> dump, ALWAYS! I have sup-dump in my backup2l before-hook.
Yes, I have a daily cron script for it now.
> 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?)
>
Thank you very much.
--
Carlos Garcia Campos
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x523E6462
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-11-14 13:35 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
2009-11-14 13:22 ` Carlos Garcia Campos [this message]
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=1258204741-sup-4254@charmaleon \
--to=carlosgc@gnome.org \
--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