[
https://issues.apache.org/jira/browse/HDFS-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee updated HDFS-4993:
-----------------------------
Resolution: Fixed
Fix Version/s: 2.1.1-beta
0.23.10
3.0.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thanks for the patch, Rob. I've committed this to branch-0.23, branch-2,
branch-2.1-beta and trunk.
> 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
