[Gluster-devel] Encountered "Directory not empty" error during remove a directory in .trashcan

Sakshi Bansal sabansal at redhat.com
Fri Jun 17 05:49:58 UTC 2016


Hi,

We need some more information regarding the test case:
1) Are you parallely running rm -rf or an rm -rf and ls from multiple mount points?
2) On the bricks do you see the directories holding files or directories?

----- Original Message -----
From: "Deng ShaoHui" <cosmo.mapanje at gmail.com>
To: gluster-devel at gluster.org
Sent: Friday, June 17, 2016 8:08:12 AM
Subject: [Gluster-devel] Encountered "Directory not empty" error during remove a directory in .trashcan

Hi: 

Recently I encountered an error msg "Directory not empty" during I execute "rm -rf" command in .trashcan. 
I used glusterfs 3.7.6. 

Here is my reproducer: 
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 itimmediately.
[root at cosmo eee]# ls -a
.  ..  php-5.6.19  php-5.6.19.tar.gz  .trashcan
[root at cosmo eee]# rm -rf php-5.6.19
[root at cosmo eee]# ls -a
.  ..  php-5.6.19.tar.gz  .trashcan

4. I could find it in .trashcan path.
[root at cosmo .trashcan]# ls
internal_op  php-5.6.19

5. I intend to delete them in .trashcan.
[root at 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. 

Is there anyone hit this issues before? Or I mistake some steps? 
Thank you. 

BR 



_______________________________________________
Gluster-devel mailing list
Gluster-devel at gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


More information about the Gluster-devel mailing list