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 "Yuval Degani (Jira)" <ji...@apache.org> on 2019/12/03 22:08: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=16987303#comment-16987303 ]
Yuval Degani commented on HDFS-15009:
-------------------------------------
[~ayushtkn], [~hemanthboyina], would you mind backporting this patch to branch-2? seems highly relevant
> 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
> Fix For: 3.3.0
>
> Attachments: HDFS-15009.001.patch, HDFS-15009.002.patch, HDFS-15009.003.patch, HDFS-15009.004.patch
>
>
> Scenario : if we have two directories dir1, dir10 and only dir10 have corrupt files
> Now if we run -list-corruptfileblocks for dir1, corrupt files count for dir1 showing is of dir10
> {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