Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <100174143.424431269315447254.JavaMail.jira@brutus.apache.org>
Date: Tue, 23 Mar 2010 03:37:27 +0000 (UTC)
From: =?utf-8?Q?Andr=C3=A9_Oriani_=28JIRA=29?= <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Updated: (HDFS-1032) Extend DFSck with an option to list
 corrupt files using API from HDFS-729
In-Reply-To: <875908419.167721268183787985.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/HDFS-1032?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andr=C3=A9 Oriani updated HDFS-1032:
-------------------------------

    Status: Open  (was: Patch Available)

canceling patch in order to force it to be sent to hudson again . It was se=
nt to hadoop5 but it seems the machine is down

> Extend DFSck with an option to list corrupt files using API from HDFS-729
> -------------------------------------------------------------------------
>
>                 Key: HDFS-1032
>                 URL: https://issues.apache.org/jira/browse/HDFS-1032
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: tools
>            Reporter: Rodrigo Schmidt
>            Assignee: Andr=C3=A9 Oriani
>         Attachments: hdfs-1032_aoriani.patch, hdfs-1032_aoriani_2.patch
>
>
> HDFS-729 created a new API to namenode that returns the list of corrupt f=
iles.
> We can now extend fsck (DFSck.java) to add an option (e.g. --list_corrupt=
) that queries the namenode using the new API and lists the corrupt blocks =
to the users.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.