[ https://issues.apache.org/jira/browse/HDFS-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354165#comment-14354165 ]
Hadoop QA commented on HDFS-979: -------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12484010/HDFS-979-take3.txt against trunk revision 82db334. {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9807//console This message is automatically generated. > FSImage should specify which dirs are missing when refusing to come up > ---------------------------------------------------------------------- > > Key: HDFS-979 > URL: https://issues.apache.org/jira/browse/HDFS-979 > Project: Hadoop HDFS > Issue Type: Improvement > Components: namenode > Affects Versions: 0.22.0 > Reporter: Steve Loughran > Assignee: Jim Plush > Priority: Minor > Attachments: HDFS-979-take1.txt, HDFS-979-take2.txt, > HDFS-979-take3.txt > > > When {{FSImage}} can't come up as either it has no data or edit dirs, it > tells me this > {code} > java.io.IOException: All specified directories are not accessible or do not > exist. > {code} > What it doesn't do is say which of the two attributes are missing. This would > be beneficial to anyone trying to track down the problem. Also, I don't think > the message is correct. It's bailing out because dataDirs.size() == 0 || > editsDirs.size() == 0 , because a list is empty -not because the dirs aren't > there, as there hasn't been any validation yet. > More useful would be > # Explicit mention of which attributes are null > # Declare that this is because they are not in the config -- This message was sent by Atlassian JIRA (v6.3.4#6332)