From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] DatabaseCorruptError
Date: Wed, 11 May 2011 00:36:54 +0000 [thread overview]
Message-ID: <1305074074-sup-8794@masanjin.net> (raw)
In-Reply-To: <20110506220650.GA23223@pimlott.net>
Reformatted excerpts from Andrew Pimlott's message of 2011-05-06:
> Sup had been running for a while, and I just came back to my terminal to
> find it dead:
>
> --- IOError from thread: periodic poll
> DatabaseError: Error reading block 4279173482: got end of file
> I'm running an old git pull from next, commit 1bafcf6 dated 2010-10-12.
Yipes. Are you out of disk space, or anything like that?
> Anything I should do to try to diagnose and recover this? Or just
> load from sup-dump?
Not knowing very much about Xapian, I suggest sup-dump. Not a great
solution, I know. Wait for heliotrope to solve your problems (or at
least be something I understand and can fix).
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-05-11 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 22:06 Andrew Pimlott
2011-05-11 0:36 ` William Morgan [this message]
2011-05-11 6:14 ` Andrew Pimlott
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=1305074074-sup-8794@masanjin.net \
--to=wmorgan-sup@masanjin.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