[ https://issues.apache.org/jira/browse/HDFS-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845182#action_12845182 ]
dhruba borthakur commented on HDFS-1032: ---------------------------------------- Since the namenode API does not list all corupted files: instead of saying out.println("Corrupted files:"); how about something like this: out.println("Here are a few files that may be corrupted:"); Similarly, instead of out.println("There is no corrupted files in the filesystem under path '" + path + "' "); out.println("There are no corrupted files under " + path) Also, if a user specifies -corruptedfiles along with -files -blocks -locations, then it should generate an error. The -corruptedfiles option cannot be combined with any other option. > Extend DFSck with an option to list corrupt files using API from HDFS-729 > ------------------------------------------------------------------------- > > Key: HDFS-1032 > URL: https://issues.apache.org/jira/browse/HDFS-1032 > Project: Hadoop HDFS > Issue Type: Improvement > Components: tools > Reporter: Rodrigo Schmidt > Attachments: hdfs-1032_aoriani.patch > > > HDFS-729 created a new API to namenode that returns the list of corrupt files. > We can now extend fsck (DFSck.java) to add an option (e.g. --list_corrupt) > that queries the namenode using the new API and lists the corrupt blocks to > the users. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.