You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Ayush Saxena (Jira)" <ji...@apache.org> on 2019/11/22 09:56:00 UTC
[jira] [Commented] (HDFS-15009) FSCK "-list-corruptfileblocks"
return Invalid Entries
[ https://issues.apache.org/jira/browse/HDFS-15009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16980026#comment-16980026 ]
Ayush Saxena commented on HDFS-15009:
-------------------------------------
Seems could be problem with the startsWith()
Remember solving some thing similar .
Just on a lighter note, can you change the directory name in the descriptions, maybe dir1 and dir10 also should be ur case?
fsck and fsckK made little difficult to understand
> FSCK "-list-corruptfileblocks" return Invalid Entries
> -----------------------------------------------------
>
> Key: HDFS-15009
> URL: https://issues.apache.org/jira/browse/HDFS-15009
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: hemanthboyina
> Assignee: hemanthboyina
> Priority: Major
>
> Scenario : if we have two directories fsck , fsckK and only fsckK have corrupt files
> Now if we run -list-corruptfileblocks for fsck dir, corrupt files count for fsck showing is of fsckK
> {code:java}
> while (blkIterator.hasNext()) {
> BlockInfo blk = blkIterator.next();
> final INodeFile inode = getBlockCollection(blk);
> skip++;
> if (inode != null) {
> String src = inode.getFullPathName();
> if (src.startsWith(path)){
> corruptFiles.add(new CorruptFileBlockInfo(src, blk));
> count++;
> if (count >= DEFAULT_MAX_CORRUPT_FILEBLOCKS_RETURNED)
> break;
> }
> }
> } {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org