+++ This bug was initially created as a clone of Bug #1264849 +++ Description of problem: The creation of trash directory will performed only when it is enabled. And similarly operations such as rename , deletion will be prevented only when it is enabled. If creation fails (by some how) then trash xlator will off by throwing a warning message. The same is applicable for internal op directory. --- Additional comment from Vijay Bellur on 2015-10-12 09:00:59 EDT --- REVIEW: http://review.gluster.org/12256 (features/trash : create trash directory only when it is enabled) posted (#2) for review on master by jiffin tony Thottan (jthottan) --- Additional comment from Vijay Bellur on 2016-03-28 05:44:13 EDT --- REVIEW: http://review.gluster.org/12256 (features/trash : create trash directory only when it is enabled) posted (#3) for review on master by jiffin tony Thottan (jthottan) --- Additional comment from Mike McCune on 2016-03-28 18:50:27 EDT --- This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
As per the conversation with the patch owner, moving this bug for 3.2
Upstream patch https://review.gluster.org/#/c/12256/ merged.
Able to delete the trash directory for older volume shares and in fresh volume the trash directory is not created by default. Version -------- glusterfs-3.12.2-5.el7rhgs.x86_64 samba-4.7.5-103.el7rhgs.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2607
great
So,Great information thanks for sharing, don't hesitate to Read more.