From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.142.125.10 with SMTP id x10cs253057wfc; Tue, 14 Jun 2011 10:35:19 -0700 (PDT) Received: by 10.52.180.169 with SMTP id dp9mr3485505vdc.134.1308072918171; Tue, 14 Jun 2011 10:35:18 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id n6si10661721vdf.25.2011.06.14.10.35.16; Tue, 14 Jun 2011 10:35:17 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id B7373185838E for ; Tue, 14 Jun 2011 13:35:16 -0400 (EDT) Received: from masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 282B71858367 for ; Tue, 14 Jun 2011 13:21:15 -0400 (EDT) Received: from w by masanjin.net with local (Exim 4.71) (envelope-from ) id 1QWXRg-0007dO-62 for sup-devel@rubyforge.org; Tue, 14 Jun 2011 17:30:32 +0000 From: William Morgan To: sup-devel In-reply-to: References: Date: Tue, 14 Jun 2011 17:30:32 +0000 Message-Id: <1308071162-sup-7051@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-devel] Tokyo Cabinet fails with invalid record header X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org 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.) -- William _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel