[
https://issues.apache.org/jira/browse/HDFS-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907757#comment-13907757
]
Jing Zhao commented on HDFS-5988:
---------------------------------
Hi Andrew, I think you're right: getLayoutVersion() returns the layout version
of the old fsimage, but we should update the current inode map any way.
Thanks for the fix. +1 for the patch.
> Bad fsimage always generated after upgrade
> ------------------------------------------
>
> Key: HDFS-5988
> URL: https://issues.apache.org/jira/browse/HDFS-5988
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.4.0
> Reporter: Andrew Wang
> Assignee: Andrew Wang
> Priority: Blocker
> Attachments: hdfs-5988-1.patch
>
>
> Internal testing revealed an issue where, after upgrading from an earlier
> release, we always fail to save a correct PB-based fsimage (namely, missing
> inodes leading to an inconsistent namespace). This results in substantial
> data loss, since the upgraded fsimage is broken, as well as the fsimages
> generated by saveNamespace and checkpointing.
> This ended up being a bug in the old fsimage loading code, patch coming.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
