[HADOOP-745] NameNode throws FileNotFoundException: Parent path does not exist on startup

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8.0
• Fix Version/s: 0.10.0
• Assignee: Dhruba Borthakur
• Reporter: Nigel Daley
• Created: 22/Nov/06 23:38
• Updated: 08/Jul/09 16:42
• Resolved: 03/Jan/07 18:48

Description

(with credit to Christian)

The following exception is reported by the namenode upon startup:

2006-11-22 12:18:17,713 ERROR org.apache.hadoop.dfs.NameNode:
java.io.FileNotFoundException: Parent path does not exist: /foo/bar
at org.apache.hadoop.dfs.FSDirectory$INode.addNode(FSDirectory.java:186)
at org.apache.hadoop.dfs.FSDirectory.unprotectedMkdir(FSDirectory.java:731)
at org.apache.hadoop.dfs.FSEditLog.loadFSEdits(FSEditLog.java:254)
at org.apache.hadoop.dfs.FSImage.loadFSImage(FSImage.java:191)
at org.apache.hadoop.dfs.FSDirectory.loadFSImage(FSDirectory.java:321)
at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:230)
at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:145)
at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:137)
at org.apache.hadoop.dfs.NameNode.main(NameNode.java:585)

Perhaps the 'mkdirs' section

INode inserted = unprotectedMkdir(cur);
if (inserted != null) {
NameNode.stateChangeLog.debug("DIR* FSDirectory.mkdirs: "
+"created directory "+cur );
fsImage.getEditLog().logMkDir( inserted );

needs to be synchronized or the unprotectedMkdir method needs to be changed
to allow creating missing parent directories.