From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.142.125.10 with SMTP id x10cs226304wfc; Mon, 13 Jun 2011 19:37:23 -0700 (PDT) Received: by 10.229.131.32 with SMTP id v32mr4422380qcs.35.1308019042551; Mon, 13 Jun 2011 19:37:22 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id m24si9932497qck.44.2011.06.13.19.37.22; Mon, 13 Jun 2011 19:37:22 -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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 1D28F159808A for ; Mon, 13 Jun 2011 22:37:22 -0400 (EDT) Received: from mail-vx0-f178.google.com (mail-vx0-f178.google.com [209.85.220.178]) by rubyforge.org (Postfix) with ESMTP id 90A3B1858372 for ; Mon, 13 Jun 2011 22:37:15 -0400 (EDT) Received: by vxc11 with SMTP id 11so5521941vxc.23 for ; Mon, 13 Jun 2011 19:37:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=mNfOhzjxMVTiyy492aLGrkwuP+SOLHyPf76zvX6LUkM=; b=M6zpcNaoSRcHTFjMHsyBsdINwc3V3gsDSAst8y1+r0+wUpQaKYuhzcYTDRZxhbrywn g5kLRGXh3ofmnvihGg0Rb742jf0JD+6VlPRQUMdUPZNCWmcbnEFTR8CCVpzzzQayM99D 0kAMDthqYD8uHnkAvRNigigYL8OO6m2hGHdrg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=MqCOJw5T+W6BL79fQ52ASw5fPg+s0HNP3rdJEaTwSGo5jW3LknyB1Sc3Yl399My7Dc dtR/T8WBMRSd2bGgiplEnpRUkBohBRNbDDXFHIzzzOZhj9VuflouH/ejvIUjfTINRSGd +pOzExkaVKner8yMxIgp6xof/oBNFrE0jvloQ= MIME-Version: 1.0 Received: by 10.52.96.5 with SMTP id do5mr948938vdb.67.1308019034960; Mon, 13 Jun 2011 19:37:14 -0700 (PDT) Received: by 10.52.184.225 with HTTP; Mon, 13 Jun 2011 19:37:14 -0700 (PDT) In-Reply-To: <1308017654-sup-350@masanjin.net> References: <1308017442-sup-8849@masanjin.net> <1308017654-sup-350@masanjin.net> Date: Tue, 14 Jun 2011 11:37:14 +0900 Message-ID: From: Horacio Sanson To: Sup developer discussion 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org 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. regards, Horacio On Tue, Jun 14, 2011 at 11:14 AM, William Morgan wrote: > Whoops, I mean this: > > http://www.supermind.org/blog/554/2gb-limit-with-tokyo-cabinet-aka-invalid-meta-data > -- > William > _______________________________________________ > Sup-devel mailing list > Sup-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/sup-devel > _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel