Details
-
New Feature
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
As now the fsck can do pretty well,but when the developer happened to the log such Block blk_28622148 is not valid.etc
We wish to know which file and the datanodes the block belongs to.It can be solved by running "bin/hadoop fsck -files -blocks -locations / | grep <blockid>" ,but as mentioned early in the HADOOP-4945 ,it's not an effective way in a big product cluster.
so maybe we could do something to let the fsck more convenience .
Attachments
Attachments
Issue Links
- is a clone of
-
HADOOP-4945 Add BlockTool to query file and its block info
- Closed