Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 84509 invoked from network); 4 Mar 2010 20:22:10 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 Mar 2010 20:22:10 -0000 Received: (qmail 92639 invoked by uid 500); 4 Mar 2010 20:21:58 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 92438 invoked by uid 500); 4 Mar 2010 20:21:58 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 92430 invoked by uid 99); 4 Mar 2010 20:21:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Mar 2010 20:21:58 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of saint.ack@gmail.com designates 209.85.221.204 as permitted sender) Received: from [209.85.221.204] (HELO mail-qy0-f204.google.com) (209.85.221.204) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Mar 2010 20:21:50 +0000 Received: by qyk42 with SMTP id 42so500162qyk.29 for ; Thu, 04 Mar 2010 12:21:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=T+djYgZ3jIJM7/L0EGqS/wke8rlvsPMrC7C9vWRA7v8=; b=Ig3BKavF8wBy6etnkOUcqJBFxuwHyFOD6zXmoGl//qEgFrqODcONfzU/t4GEDXwz9s RaAvuigiq8rRXNn+/7w0e6KIDc8dGvgV1zDLEWU68vWEQX7WzIQNrEoHdcPHlFIMF0ae exLeROAVosnvN8Zq0RX9A/Nc2DA1HYr/Xp/8k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=d53RTkrioXEboURF97IDXx8i7Gzhjm7Am5VWjYuCFDSMZc27Ma19aRG9tGoLQqEXX9 NeuRsyzB94CGEUEtBced1Et4yP6Lj5T4BwHljQu70W4XcNkxwwpHBAqitpbdOPIJWvUK pT277MuQfRl2BTRig9sZ6PhHpkfvj2pZr7tvc= MIME-Version: 1.0 Sender: saint.ack@gmail.com Received: by 10.229.213.144 with SMTP id gw16mr1741159qcb.3.1267734089008; Thu, 04 Mar 2010 12:21:29 -0800 (PST) In-Reply-To: <2986c2f31003041219x1d1dce9frdfc1a4dc334f89ac@mail.gmail.com> References: <2986c2f31003041219x1d1dce9frdfc1a4dc334f89ac@mail.gmail.com> Date: Thu, 4 Mar 2010 12:21:28 -0800 X-Google-Sender-Auth: dc24c087077e1884 Message-ID: <7c962aed1003041221m529b7b01q685fa9d0b3ab3184@mail.gmail.com> Subject: Re: starting hbase after losing data on hadoop namenode From: Stack To: hbase-user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org If you run fsck on your hdfs, whats it say? St.Ack On Thu, Mar 4, 2010 at 12:19 PM, mike anderson wro= te: > Yesterday my namenode went down because of =A0a lack of hard disk space. > I was able to get the namenode started again by removing the edits.new > file and sacrificing some of the data. However, I believe Hbase still > thinks this data exists, as is evident from these types of entries in > the master's log when I start it up: > > 2010-03-04 15:13:41,477 INFO org.apache.hadoop.hdfs.DFSClient: Could > not obtain block blk_-4089156066204357637_60829 from any node: > java.io.IOException: No live nodes contain current block > > Which tools should I use to fix these problems? compact? Or will hbase > fix itself? > > Thanks, > Mike >