From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.142.125.10 with SMTP id x10cs227160wfc; Mon, 13 Jun 2011 20:30:09 -0700 (PDT) Received: by 10.224.201.130 with SMTP id fa2mr4347783qab.364.1308022208162; Mon, 13 Jun 2011 20:30:08 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id gy9si9400738qab.40.2011.06.13.20.30.06; Mon, 13 Jun 2011 20:30:07 -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 B268418583A6 for ; Mon, 13 Jun 2011 23:30:06 -0400 (EDT) Received: from masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 7C06A18581B2 for ; Mon, 13 Jun 2011 23:21:43 -0400 (EDT) Received: from w by masanjin.net with local (Exim 4.71) (envelope-from ) id 1QWKLC-0006qc-Rv for sup-devel@rubyforge.org; Tue, 14 Jun 2011 03:30:58 +0000 From: William Morgan To: sup-devel In-reply-to: References: <1308017442-sup-8849@masanjin.net> <1308017654-sup-350@masanjin.net> Date: Tue, 14 Jun 2011 03:30:58 +0000 Message-Id: <1308022018-sup-5391@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-devel] Invalid meta data error in OklahomaMixer 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: > Not even close... my store.tch is 76MB only. This metadata corruption > in Tokyo Cabinet seems to be a common occurrence and what is scary > about this is that there seems to be no way to recover from it (as far > as google can tell). The only option I see is delete my store/index > and restart sync again. Can you point me to some links about this type of corruption? I'm far from wedded to Oklahoma Mixer / Tokyo Cabinet. It was just the easiest thing to get started with. Any kind of mutable persistent key-value store will do. Other alternatives to consider: another TokyoCabinet gem besides OH, KyotoCabinet, BDB... I kinda don't want to move to separate processes like Redis though. If only there were a libredis (well there is, but it's not what you want.) -- William _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel