Return-Path: 
 <user-return-12397-apmail-hadoop-common-user-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-common-user-archive@www.apache.org
Delivered-To: apmail-hadoop-common-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 97AC01035C
	for <apmail-hadoop-common-user-archive@www.apache.org>;
 Tue, 10 Dec 2013 00:33:10 +0000 (UTC)
Received: (qmail 42902 invoked by uid 500); 10 Dec 2013 00:33:05 -0000
Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org
Received: (qmail 42820 invoked by uid 500); 10 Dec 2013 00:33:05 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Received: (qmail 42813 invoked by uid 99); 10 Dec 2013 00:33:05 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Dec 2013 00:33:05 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of justlooks@gmail.com designates
 209.85.216.52 as permitted sender)
Received: from [209.85.216.52] (HELO mail-qa0-f52.google.com) (209.85.216.52)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Dec 2013 00:32:58 +0000
Received: by mail-qa0-f52.google.com with SMTP id cm18so1563496qab.18
        for <user@hadoop.apache.org>; Mon, 09 Dec 2013 16:32:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=9z1tjmna0C8MZq6NaYEy3twoD6zIyFZGNyj8YprY/14=;
        b=UAaz/OUxS8ef+g7zFufc+JsgW5N4DstX36vEbHN/O2I3UHJSZDIsxqakWe+GHCQXM0
         Gy1He4ts8RRCwBJ0tbCXYdGlgIb3c6yTuEsUDbII40Iquy19SWSQLld7zeBUL4Ry9qh+
         yBRz4iN9Q9eEpLRUvBcfPpRq2kdlQCx2MXMHqIPKIT5zauhF/IkU32o1Tw1z96tW1yxV
         LBRv/hBK6zMAa9vqZiG8Ahjgy8NKUkxpYq88XjQb3LoTFhYw1gjOS9nn8bB5NBNwd69i
         nnQsW/m+yruEx9VVyjv3DFj+OYSnVY+o08u5fDtQxSMwqACZsrvE+0x9cd0aio8mDlaU
         15dg==
MIME-Version: 1.0
X-Received: by 10.224.4.70 with SMTP id 6mr38902434qaq.86.1386635558141; Mon,
 09 Dec 2013 16:32:38 -0800 (PST)
Received: by 10.140.20.37 with HTTP; Mon, 9 Dec 2013 16:32:38 -0800 (PST)
Date: Tue, 10 Dec 2013 08:32:38 +0800
Message-ID: 
 <CACeqxwQEe4xSHTjkZ4tVTXejf+F+YYwSybw9jGOyrgCzHcjH=Q@mail.gmail.com>
Subject: how to handle the corrupt block in HDFS?
From: ch huang <justlooks@gmail.com>
To: user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=001a11c21cc8e0465d04ed233f87
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c21cc8e0465d04ed233f87
Content-Type: text/plain; charset=ISO-8859-1

hi,maillist:
            my nagios alert me that there is a corrupt block in HDFS all
day,but i do not know how to remove it,and if the HDFS will handle this
automaticlly? and if remove the corrupt block will cause any data
lost?thanks

--001a11c21cc8e0465d04ed233f87
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>hi,maillist:</div>
<div>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 my nagios alert me that there is a c=
orrupt block in HDFS all day,but i do not know how to remove it,and if the =
HDFS will handle this automaticlly? and if remove the corrupt block will ca=
use any data lost?thanks</div>

--001a11c21cc8e0465d04ed233f87--