You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2015/10/05 21:46:27 UTC
[jira] [Commented] (HDFS-9138)
TestDatanodeStartupFixesLegacyStorageIDs fails on Windows due to failure to
unpack old image tarball that contains hard links
[ https://issues.apache.org/jira/browse/HDFS-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943915#comment-14943915 ]
Colin Patrick McCabe commented on HDFS-9138:
--------------------------------------------
[~cnauroth], just out of curiosity, what was the resolution on Windows? Do we create the hardlinks there, or do we swap in the referenced file?
> TestDatanodeStartupFixesLegacyStorageIDs fails on Windows due to failure to unpack old image tarball that contains hard links
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-9138
> URL: https://issues.apache.org/jira/browse/HDFS-9138
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Priority: Minor
> Attachments: HDFS-9138.001.patch
>
>
> {{TestDatanodeStartupFixesLegacyStorageIDs#testUpgradeFrom22via26FixesStorageIDs}} uses a checked-in DataNode data directory that contains hard links. The hard links cannot be handled correctly by the commons-compress library used in the Windows implementation of {{FileUtil#unTar}}. The result is that the unpacked block files have 0 length, the block files reported to the NameNode are invalid, and therefore the mini-cluster never gets enough good blocks reported to leave safe mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)