[ https://issues.apache.org/jira/browse/HDFS-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735869#comment-13735869 ]
Hudson commented on HDFS-4993: ------------------------------ FAILURE: Integrated in Hadoop-Hdfs-0.23-Build #695 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/695/]) HDFS-4993. fsck can fail if a file is renamed or deleted. Contributed by Robert Parker. (kihwal: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1512456) * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NamenodeFsck.java * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFsck.java > fsck can fail if a file is renamed or deleted > --------------------------------------------- > > Key: HDFS-4993 > URL: https://issues.apache.org/jira/browse/HDFS-4993 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 3.0.0, 2.1.0-beta, 0.23.9 > Reporter: Kihwal Lee > Assignee: Robert Parker > Fix For: 3.0.0, 0.23.10, 2.1.1-beta > > Attachments: HDFS-4993-branch_0.23.patch, HDFS-4993.patch > > > In NamenodeFsck#check(), the getListing() and getBlockLocations() are not > synchronized, so the file deletions or renames at the right moment can cause > FileNotFoundException and failure of fsck. > Instead of failing, fsck should continue. Optionally it can record file > system modifications it encountered, but since most modifications during fsck > are not detected, there might be little value in recording these specifically. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira