Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Subject: Re: [jira] Lantao Jin shared "HDFS-11102: Deleting .Trash without
 -skipTrash should be confirmed" with you
To: user@hadoop.apache.org
References: <465228157.20373.1478242078367.JavaMail.jiratomcat@arcas>
From: Sambaiah Kilaru <ksambaiah@ksambaiah.org>
Message-ID: <186743fc-4b71-191b-a824-c0f6823271b9@ksambaiah.org>
Date: Tue, 8 Nov 2016 15:42:26 +0530
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0)
 Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <465228157.20373.1478242078367.JavaMail.jiratomcat@arcas>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
archived-at: Tue, 08 Nov 2016 10:13:47 -0000

expunge is safe option. I do -rm -r and some times wanted to clean, run 
expunge command.


On 11/4/16 12:17 PM, Lantao Jin (JIRA) wrote:
>      Lantao Jin shared an issue with you
>      -----------------------------------
>
>      
>
>> Deleting .Trash without -skipTrash should be confirmed
>> ------------------------------------------------------
>>
>>                  Key: HDFS-11102
>>                  URL: https://issues.apache.org/jira/browse/HDFS-11102
>>              Project: Hadoop HDFS
>>           Issue Type: Improvement
>>           Components: hdfs
>>             Reporter: Lantao Jin
>>
>> As a Hadoop DEVOPS, I saw lots of cases that user delete their data by mistake.  Most of them can be recovered from trash but the rest ones were not luck.
>> A system can’t guess user's purpose，but a good system should help user to avoid their mistakes.
>> There is a very common case like:
>> If a user want to delete some dir from HDFS, they may use:
>> {code}
>> hadoop -fs -rm -r /user/someone/pathToBeDelete
>> {code}
>> The directory /user/someone/pathToBeDelete will move into
>> {code}
>> /user/someone/.Trash/current/user/someone/pathToBeDelete
>> {code}
>> If user want delete it permanently, option "-skipTrash" can be attached. That's the design and Hadoop knows the user's purpose well.
>> Usually, user didn't use "skipTrash" for safety consideration. That's good till now.
>> But the purpose is to delete some data for saving more space. Then the user begin to delete it from Trash with the below command:
>> {code}
>> hadoop -fs -rm -r /user/someone/ .Trash
>> {code}
>> Why not just delete "/user/someone/.Trash/current/user/someone/pathToBeDelete" is that because the user knows only pathToBeDelete in trash directory now.
>> The trash include pathToBeDelete will be deleted permanently.
>> *But Wait! Do you see the blank space before the dot?*
>> If you also type this command by "copy-paste" include some space or invisible char, the whole /user/someone directory and the whole /user/someone/.Trash will be deleted unfortunately. *Jesus, that's means the directory /user/someone is deleted permanently and unexpectedly!*
>> So I think *any ".Trash" word appears in the "rm" command without "skip" should be launched a double checking by system to help people to avoid their mistake.*
>> If you also agree this design, I will offer a patch.
>       Also shared with
>            hdfs-issues@hadoop.apache.org
>            hdfs-dev@hadoop.apache.org
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: user-help@hadoop.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@hadoop.apache.org
For additional commands, e-mail: user-help@hadoop.apache.org