You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Harsh J (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/18 10:43:40 UTC

[jira] [Resolved] (HDFS-319) Add option to fsck that checks the crc

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

Harsh J resolved HDFS-319.
--------------------------

    Resolution: Cannot Reproduce

Bad block lengths are indeed picked up by the DNs today and reported promptly.
                
> Add option to fsck that checks the crc
> --------------------------------------
>
>                 Key: HDFS-319
>                 URL: https://issues.apache.org/jira/browse/HDFS-319
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Johan Oskarsson
>            Assignee: Sameer Paranjpye
>
> If I'm not mistaken the fsck command doesn't actually check the crc of the blocks.
> I just had a problem where a few blocks managed to get the size 0, fsck didn't report this but
> my hadoop programs started failing because some of the input data was corrupted.
> An option in the fsck program to actually check the crc would be nice, even though it would take a while to run.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira