hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Prakash (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2848) hdfs corruption appended to blocks is not detected by fs commands or fsck
Date Thu, 02 Feb 2012 16:58:51 GMT

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

Ravi Prakash commented on HDFS-2848:
------------------------------------

BlockPoolSliceScanner is not going to detect this kind of corruption either. BlockPoolSliceScanner.java:406
{noformat}
        blockSender = new BlockSender(block, 0, -1, false, true, datanode,
            null);
{noformat}
Its using BlockSender with verifyChecksum set to be true. But that code still picks up the
block replica size from replicasMap which is WRONG (after corruption).

So the periodic (by default once every 3 weeks) scan won't detect the corruption either.
                
> hdfs corruption appended to blocks is not detected by fs commands or fsck
> -------------------------------------------------------------------------
>
>                 Key: HDFS-2848
>                 URL: https://issues.apache.org/jira/browse/HDFS-2848
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 0.23.0
>            Reporter: Ravi Prakash
>            Assignee: Ravi Prakash
>
> Courtesy Pat White [~patwhitey2007]
> {quote}
> Appears that there is a regression in corrupt block detection by both fsck and fs cmds
like 'cat'. Testcases for
> pre-block and block-overwrite corruption of all replicas is correctly reporting errors
however post-block corruption is
> not, fsck on the filesystem reports it's Healthy and 'cat' returns without error. Looking
at the DN blocks themselves,
> they clearly contain the injected corruption pattern.
> {quote}

--
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

        

Mime
View raw message