Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 51962 invoked from network); 14 Dec 2006 04:25:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Dec 2006 04:25:40 -0000 Received: (qmail 44288 invoked by uid 500); 14 Dec 2006 04:25:46 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 44253 invoked by uid 500); 14 Dec 2006 04:25:45 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 44244 invoked by uid 99); 14 Dec 2006 04:25:45 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Dec 2006 20:25:45 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Dec 2006 20:25:02 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 352AC7140F6 for ; Wed, 13 Dec 2006 20:24:23 -0800 (PST) Message-ID: <11945271.1166070263215.JavaMail.jira@brutus> Date: Wed, 13 Dec 2006 20:24:23 -0800 (PST) From: "Doug Cutting (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Commented: (HADOOP-432) support undelete, snapshots, or other mechanism to recover lost files In-Reply-To: <13436198.1155057493889.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ http://issues.apache.org/jira/browse/HADOOP-432?page=comments#action_12458360 ] Doug Cutting commented on HADOOP-432: ------------------------------------- > the namenode would thus need to export an API similar to 'find /trash -mmin +n' First, listing all the files in the trash every half hour or so shouldn't be too big of a burden. Even if it is, then we could create a sub-directory for each ten-minute interval, named by its time of creation. Then one could quickly find all files that need to be deleted without listing the full trash. > You'd also need an efficient way to get the size of the trash externally. We already support server-side du for directories in DFS. Calling it every half hour or even every ten minutes on the trash should not be too great of a burden. So I'd still prefer to see this as a FileSystem-independent implementation. > support undelete, snapshots, or other mechanism to recover lost files > --------------------------------------------------------------------- > > Key: HADOOP-432 > URL: http://issues.apache.org/jira/browse/HADOOP-432 > Project: Hadoop > Issue Type: Improvement > Components: dfs > Reporter: Yoram Arnon > Assigned To: Wendy Chien > Attachments: undelete12.patch, undelete16.patch, undelete17.patch > > > currently, once you delete a file it's gone forever. > most file systems allow some form of recovery of deleted files. > a simple solution would be an 'undelete' command. > a more comprehensive solution would include snapshots, manual and automatic, with scheduling options. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira