[
https://issues.apache.org/jira/browse/HDFS-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789653#action_12789653
]
Raghu Angadi commented on HDFS-729:
-----------------------------------
Hi Dhruba,
Patch looks good. What would be an alternative for "badFile"? A "corruptFile",
might not imply "one of the blocks no good replica". But in general, "corrupt
file" implies something that could not be recovered by filesystem. Between
these two, my vote is for "corruptFile".
The current API is fine : one minor nit is that even when it returns less than
numExpectedFiles it does not imply there aren't any more.
In practice, it is probably good enough not to have this limit and always
return up to (100 or 500 files).. This would simplify the interface. Your
choice.
I will double check if all the blocks in 'pri 2' bucket includes all the and
only the blocks with no good replica left.
> fsck option to list only corrupted files
> ----------------------------------------
>
> Key: HDFS-729
> URL: https://issues.apache.org/jira/browse/HDFS-729
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Attachments: badFiles.txt, badFiles2.txt, corruptFiles.txt
>
>
> An option to fsck to list only corrupted files will be very helpful for
> frequent monitoring.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
