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 AD7A6DEC7 for ; Fri, 2 Nov 2012 16:17:16 +0000 (UTC) Received: (qmail 45792 invoked by uid 500); 2 Nov 2012 16:17:16 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 45757 invoked by uid 500); 2 Nov 2012 16:17:16 -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 45747 invoked by uid 99); 2 Nov 2012 16:17:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2012 16:17:16 +0000 Date: Fri, 2 Nov 2012 16:17:16 +0000 (UTC) From: "Suresh Srinivas (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <586914470.60941.1351873036481.JavaMail.jiratomcat@arcas> In-Reply-To: <600033870.49553.1326826119648.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-2802) Support for RW/RO snapshots in HDFS 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-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489516#comment-13489516 ] Suresh Srinivas commented on HDFS-2802: --------------------------------------- Konstantin, missed a few comments: bq. Same with ls -r. I see Aaron proposes to skip .snapshot, which makes sense. Should we have something like ls -rs to list snapshotable directories in the tree? .snapshot is skipped when regular path is given. Let me go over some examples: # related operations that does not include .snapshot only operates on non snapshot related files. #* ls -r - will only list non snapshot files #* rm -r - as already stated in the document, if there are snapshots under that path, then deletion is not allowed, until all the snapshots are deleted. # /.snapshot applies to all the snapshots #* ls /.snapshot - lists all the snapshots under that path #* ls -r /.snapshot - I was thinking this would be same as ls /.snapshot. I was thinking recursively listing all the snapshots could be expensive and may not be what a user wants. I want to get your thoughts on that. #* rm /.snapshot or rm -r /.snapshot - removes all the snapshots. I want to get your thoughts on this as well. # /.snapshot/snapname #* ls /.snapshot/snapname - list files in the snapshot #* ls -r /.snapshot/snapname - recursively lists all the files in the snapshot name #* rm /.snapshot/snapname or rm -r /.snapshot/snapname - deletes the snapshot #* rm /.snapshot/snapname/file - fails. snapshot is read-only. I will update the design document with these details. > Support for RW/RO snapshots in HDFS > ----------------------------------- > > Key: HDFS-2802 > URL: https://issues.apache.org/jira/browse/HDFS-2802 > Project: Hadoop HDFS > Issue Type: New Feature > Components: data-node, name-node > Reporter: Hari Mankude > Assignee: Hari Mankude > Attachments: HDFS-2802.20121101.patch, HDFS-2802-meeting-minutes-121101.txt, HDFSSnapshotsDesign.pdf, snap.patch, snapshot-design.pdf, snapshot-design.tex, snapshot-one-pager.pdf, Snapshots20121018.pdf, Snapshots20121030.pdf > > > Snapshots are point in time images of parts of the filesystem or the entire filesystem. Snapshots can be a read-only or a read-write point in time copy of the filesystem. There are several use cases for snapshots in HDFS. I will post a detailed write-up soon with with more information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira