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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/03/12 03:00:44 UTC

[jira] [Resolved] (HDFS-1029) Image corrupt with number of files = 1

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

Allen Wittenauer resolved HDFS-1029.
------------------------------------
    Resolution: Fixed

This is likely a stale issue. Closing. Reopen if you feel otherwise.


> Image corrupt with number of files = 1
> --------------------------------------
>
>                 Key: HDFS-1029
>                 URL: https://issues.apache.org/jira/browse/HDFS-1029
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 0.20.1
>            Reporter: Todd Lipcon
>
> Last week I recovered a corrupt namenode image that was completely sane except that the "number of files" in the header was set to 1, rather than the correct number (many million). The NN in question had been running for some time, so I believe the 2NN uploaded this broken image as a checkpoint. After this point, of course, no further checkpoints occurred, and the NN failed to load its image upon restart.
> Not sure how this happens - my only thought is that we may need to add synchronization on the nsCount field in INodeDirectoryWithQuota, but that's a long shot.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)