The fix proposed on
HDFS-11197 didn't cover the scenario where the EZ deleted but still under a snapshot is not a direct child of the snapshottable directory.
Here the code snippet proposed on
HDFS-11197 that would avoid the error reported by hdfs crypto -listZones when a deleted EZ is still under a given snapshot:
It will ignore EZs when it's a direct child of a snapshot, because its parent inode will be null, and it isn't the root inode. However, if the EZ is not directly under snapshottable directory, its parent will not be null, and it will pass this check, so it will fail further due absolute path required validation error.
I would like to work on a fix that would also cover this scenario.