[ 
https://issues.apache.org/jira/browse/HDFS-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934648#action_12934648
 ] 

Thanh Do commented on HDFS-89:
------------------------------

This is true for data file, if the length of a data block get truncated 
by ext3 fsck, NN will detect this because the NN knows the length
of the block. 
But we saw a case that once a meta file get truncated, 
and DN boots up, send a block report to NN, NN doesn't detect
that problem. 
This kind of corruption can only be detect by a reader, 
or a data block scanner. 


> Datanode should verify block sizes vs metadata on startup
> ---------------------------------------------------------
>
>                 Key: HDFS-89
>                 URL: https://issues.apache.org/jira/browse/HDFS-89
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Brian Bockelman
>
> I could have sworn this bug had been reported by someone else already, but I 
> can't find it on JIRA after searching.... apologies if this is a duplicate.
> The datanode, upon starting up, should check and make sure that all block 
> sizes as reported via `stat` are the same as the block sizes as reported via 
> the block's metadata.

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

Reply via email to