From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] error after leveldb-ruby upgrade
Date: Sun, 17 Jul 2011 20:05:27 +0000 [thread overview]
Message-ID: <1310933008-sup-9080@masanjin.net> (raw)
In-Reply-To: <CAOxvSbddWV33kzmS0OPCg-jvcKjzwu1JyGFjqL4Puaxiv-a=tQ@mail.gmail.com>
Reformatted excerpts from Hamish D's message of 2011-07-17:
> $ heliotrope-server -d ~/.heliotrope
> /var/lib/gems/1.9.1/gems/leveldb-ruby-0.7/lib/leveldb.rb:11:in `make':
> Corruption: checksum mismatch (LevelDB::Error)
That error gets thrown when LevelDB detects things are corrupted, but
I'd be surprised if the upgrade to 0.7 caused this--the only change was
one in how memory in the Ruby world is free'd. None of the actual
LevelDB code changed.
If you downgrade to 0.6, do you still get that error? Are you running
out of disk space, or anything like that?
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-07-17 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 17:42 Hamish D
2011-07-17 20:05 ` William Morgan [this message]
2011-07-17 22:51 ` Hamish D
2011-07-18 4:21 ` William Morgan
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=1310933008-sup-9080@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@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