Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B545F10440 for ; Wed, 27 Nov 2013 02:18:36 +0000 (UTC) Received: (qmail 33387 invoked by uid 500); 27 Nov 2013 02:18:36 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 33304 invoked by uid 500); 27 Nov 2013 02:18:36 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 32965 invoked by uid 99); 27 Nov 2013 02:18:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Nov 2013 02:18:35 +0000 Date: Wed, 27 Nov 2013 02:18:35 +0000 (UTC) From: "Jing Zhao (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-5568) Support inclusion of snapshot paths in Namenode fsck MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833361#comment-13833361 ] Jing Zhao commented on HDFS-5568: --------------------------------- Hmm. My original thought is that since we now do not support nested snapshottable directories, for a given directory, we only have at most one snapshottable directory and we should be able to check the corresponding snapshot paths. But after more thinking, looks like the challenge here is that the given directory can be a renamed directory. In that case, it is hard to identify the correct snapshot paths. So I think the current solution is good and we do not need to support that case here. > Support inclusion of snapshot paths in Namenode fsck > ---------------------------------------------------- > > Key: HDFS-5568 > URL: https://issues.apache.org/jira/browse/HDFS-5568 > Project: Hadoop HDFS > Issue Type: Improvement > Components: snapshots > Reporter: Vinay > Assignee: Vinay > Attachments: HDFS-5568-1.patch, HDFS-5568.patch, HDFS-5568.patch > > > Support Fsck to check the snapshot paths also for inconsistency. > Currently Fsck supports snapshot paths if path given explicitly refers to a snapshot path. > We have seen safemode problems in our clusters which were due to blocks missing which were only present inside snapshots. But "hdfs fsck /" shows HEALTHY. > So supporting snapshot paths also during fsck (may be by default or on demand) would be helpful in these cases instead of specifying each and every snapshottable directory. -- This message was sent by Atlassian JIRA (v6.1#6144)