[HDFS-15687] allowSnapshot fails when directory already has a Trash sub directory

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 3.4.0
• Assignee: Shashikant Banerjee
• Reporter: Nilotpal Nandi
• Created: 17/Nov/20 15:36
• Updated: 16/Dec/20 05:38
• Resolved: 16/Dec/20 05:38

Description

Steps :
1. Create an encryption zone , Trash directory would be created inside EZ directory.
/opt/cloudera/parcels/CDH/bin/hdfs crypto -createZone -keyName testkeysnapshot1605613314 -path /user/hrt_6/test_dir1/snap_encrypt_dir1605613504

2. Try to make the EZ directory snapshottable.
/opt/cloudera/parcels/CDH/bin/hdfs dfsadmin -allowSnapshot /user/hrt_6/test_dir1/snap_encrypt_dir1605613504

It fails with error :

/opt/cloudera/parcels/CDH/bin/hdfs dfsadmin -allowSnapshot /user/hrt_6/test_dir1/snap_encrypt_dir1605613504
2020-11-17 11:45:16,598|INFO|MainThread|machine.py:180 - run()||GUID=b35fc918-ed08-4c5d-92c1-c5aab449fb10|allowSnapshot: Can't provision trash for snapshottable directory /user/hrt_6/test_dir1/snap_encrypt_dir1605613504 because trash path /user/hrt_6/test_dir1/snap_encrypt_dir1605613504/.Trash already exists.
2020-11-17 11:45:16,956|INFO|MainThread|machine.py:209 - run()||GUID=b35fc918-ed08-4c5d-92c1-c5aab449fb10|Exit Code: 255

Issue Links

• is fixed by: HDFS-15689 allow/disallowSnapshot on EZ roots shouldn't fail due to trash provisioning/emptiness check