Description of problem: Encounter a "Directory not empty" error during Remove a directory in .trashcan Version-Release number of selected component (if applicable): glusterfs 3.7.6 How reproducible: Steps to Reproduce: 1. I created a volume titled "eee", then I turned the "features.trash" on. 2. Mount it on /volume/eee 3. Extract a package, let's say "php-5.6.19.tar.gz". And then I delete it immediately. [root@cosmo eee]# ls -a . .. php-5.6.19 php-5.6.19.tar.gz .trashcan [root@cosmo eee]# rm -rf php-5.6.19 [root@cosmo eee]# ls -a . .. php-5.6.19.tar.gz .trashcan 4. I could find it in .trashcan path. [root@cosmo .trashcan]# ls internal_op php-5.6.19 5. I intend to delete it in .trashcan. [root@cosmo .trashcan]# rm -rf php-5.6.19/ rm: cannot remove `php-5.6.19/Zend/tests/generators': Directory not empty rm: cannot remove `php-5.6.19/Zend/tests/constants/fixtures/folder4': Directory not empty rm: cannot remove `php-5.6.19/Zend/tests/constants/fixtures/folder3': Directory not empty rm: cannot remove `php-5.6.19/Zend/tests/traits': Directory not empty rm: cannot remove `php-5.6.19/ext/odbc': Directory not empty rm: cannot remove `php-5.6.19/ext/gettext/tests/locale/en': Directory not empty rm: cannot remove `php-5.6.19/ext/simplexml': Directory not empty rm: cannot remove `php-5.6.19/ext/curl/tests': Directory not empty 6. I checked every directory in this mount point, it seems like they all are empty. But I jumped into bricks directory which is used by this volume, I found these directorys, they are not empty, still hold some files in there. Actual results: Expected results: Additional info:
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.