[
https://issues.apache.org/jira/browse/HDFS-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708558#comment-13708558
]
Kihwal Lee commented on HDFS-4993:
----------------------------------
Koji pointed out that the following used to mask this, until a change was made
to throw a FileNotFoundException in HADOOP-6559 and HDFS-1016
{noformat}
if (thisListing == null) {
return;
}
{noformat}
> 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: 2.1.0-beta, 0.23.9
> Reporter: Kihwal Lee
>
> 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
