hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiao Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9231) fsck doesn't explicitly list when Bad Replicas/Blocks are in a snapshot
Date Fri, 23 Oct 2015 21:57:28 GMT

    [ https://issues.apache.org/jira/browse/HDFS-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14971947#comment-14971947

Xiao Chen commented on HDFS-9231:

Per the offline talk, we can make {{FSDirSnapshotOp#getSnapshotFiles}} more elegant by adding
an interface on {{Snapshot}} to get the full snapshot root path, hence eliminating the need
of pass in snapshottableDir. Attached patch 07 to do this. Thanks Yongjun.

> 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,
HDFS-9231.005.patch, HDFS-9231.006.patch, HDFS-9231.007.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

View raw message