[
https://issues.apache.org/jira/browse/HDFS-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Chen updated HDFS-9231:
----------------------------
Description:
Currently for snapshot files, {{fsck -list-corruptfileblocks}} shows corrupt
blocks with the original file dir instead of the snapshot dir, and {{fsck
-list-corruptfileblocks -includeSnapshots}} behave the same.
This can be confusing because even when the original file is deleted, fsck will
still show that deleted file as corrupted, although what's actually corrupted
is the snapshot.
As a side note, {{fsck -files -includeSnapshots}} shows the snapshot dirs.
was:
For snapshot files, fsck shows corrupt blocks with the original file dir
instead of the snapshot dir.
This can be confusing since even when the original file is deleted, a new fsck
run will still show that file as corrupted although what's actually corrupted
is the snapshot.
This is true even when given the -includeSnapshots option.
> fsck doesn't explicitly list when Bad Replicas/Blocks are in a snapshot
> -----------------------------------------------------------------------
>
> Key: HDFS-9231
> URL: https://issues.apache.org/jira/browse/HDFS-9231
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: snapshots
> Reporter: Xiao Chen
> Assignee: Xiao Chen
> Attachments: HDFS-9231.001.patch, HDFS-9231.002.patch,
> HDFS-9231.003.patch, HDFS-9231.004.patch
>
>
> Currently for snapshot files, {{fsck -list-corruptfileblocks}} shows corrupt
> blocks with the original file dir instead of the snapshot dir, and {{fsck
> -list-corruptfileblocks -includeSnapshots}} behave the same.
> This can be confusing because even when the original file is deleted, fsck
> will still show that deleted file as corrupted, although what's actually
> corrupted is the snapshot.
> As a side note, {{fsck -files -includeSnapshots}} shows the snapshot dirs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
