Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.1.0-beta, 0.23.9, 3.0.0-alpha1
-
None
-
None
-
Reviewed
Description
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.