From: Horacio Sanson <hsanson@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Tokyo Cabinet fails with invalid record header
Date: Wed, 15 Jun 2011 07:36:51 +0900 [thread overview]
Message-ID: <BANLkTi=6EuFkyDh4rjV6zroQv6k-tgH+oA@mail.gmail.com> (raw)
In-Reply-To: <1308071162-sup-7051@masanjin.net>
Interesting.... yesterday I started again to sync my gmail account
but this time using ruby1.8.7 instead of ruby1.9.1 and without any
hooks configured and it finished without problems. I think the problem
is the hooks so I will rerun again with ruby 1.9.1 but without the
hooks.
On Wed, Jun 15, 2011 at 2:30 AM, William Morgan
<wmorgan-sup@masanjin.net> wrote:
> Reformatted excerpts from Horacio Sanson's message of 2011-06-14:
>> Now the store.tch got corrupted again for some reason and the only
>> error I get is "invalid record header". Some googling does not help
>> and my previous fix (tchmgr optimiza -nl) does not fix this problem.
>> What is interesting is that the store.tch file is at 76MB now that is
>> exactly the same size it had when the previous corruption occured.
>
> Hm. And you're not running out of disk space or anything wierd like
> that, are you?
>
> Maybe you're encountering a limitation on the number of keys? What does
> this say for you?
>
> $ ruby -Ilib bin/heliotrope-console -d store
> Heliotrope console started.
> [...]
> > s = index.instance_eval { @store }
> [...]
> > s.size
> => 234201
> > s.keys.size
> => 234201
>
> (My store.tch is only 30mb.)
irb> s = index.instance_eval { @store }
irb> s.size
=> 3469212
irb> s.keys.size
=> 3469212
$ ls -lh ~/.heliotrope
合計 3.8G
drwxrwxr-x 2 ryujin ryujin 4.0K 2011-06-14 17:36 hooks
-rw-r----- 1 ryujin ryujin 4.1M 2011-06-15 07:26 index0.lb
-rw-r----- 1 ryujin ryujin 513M 2011-06-15 07:27 index0.pr
-rw-r----- 1 ryujin ryujin 13M 2011-06-15 07:28 index0.sh_
-rw-r----- 1 ryujin ryujin 65M 2011-06-15 07:27 index0.sp
-rw-r----- 1 ryujin ryujin 37M 2011-06-15 07:28 index0.th
-rw-rw-r-- 1 ryujin ryujin 3.0G 2011-06-15 07:27 messages
-rw-r--r-- 1 ryujin ryujin 378M 2011-06-15 07:28 store.tch
> --
> William <wmorgan-sup@masanjin.net>
> _______________________________________________
> Sup-devel mailing list
> Sup-devel@rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-devel
>
regards
Horacio
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-06-14 22:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 8:36 Horacio Sanson
2011-06-14 17:30 ` William Morgan
2011-06-14 22:36 ` Horacio Sanson [this message]
2011-06-15 15:11 ` William Morgan
2011-06-18 5:02 ` William Morgan
2011-06-19 13:25 ` Horacio Sanson
2011-06-19 18:30 ` William Morgan
2011-06-19 21:59 ` William Morgan
2011-06-19 22:48 ` Horacio Sanson
2011-06-20 3:54 ` William Morgan
2011-06-20 5:23 ` Horacio Sanson
2011-06-20 16:42 ` William Morgan
2011-06-20 22:26 ` Horacio Sanson
2011-06-20 22:52 ` William Morgan
2011-06-22 3:25 ` William Morgan
2011-06-22 12:38 ` Horacio Sanson
2011-06-22 18:06 ` William Morgan
2011-06-28 17:42 ` Alvaro Herrera
2011-06-29 5:18 ` William Morgan
2011-06-22 22:41 ` Horacio Sanson
2011-06-22 23:36 ` William Morgan
2011-06-23 13:29 ` Horacio Sanson
2011-06-23 15:44 ` William Morgan
2011-06-15 15:16 ` 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='BANLkTi=6EuFkyDh4rjV6zroQv6k-tgH+oA@mail.gmail.com' \
--to=hsanson@gmail.com \
--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