Description of problem: .landfill is a afr trash directory. Not sure if users are allowed to create .landfill dir. But if it is allowed rmdir, ls and cd should also be allowed. But mkdir .landfill succeeds, but ls -a doesn't list it. cd .landfill fails. and rmdir fails saying no such file or dir. But mkdir .landfill again and it complains saying file already exists. Version-Release number of selected component (if applicable): glusterfs-3.3.0qa34 How reproducible: Often Steps to Reproduce: 1. Create and start a replicated volume. And mount the volume. [root@QA-28 mnt]# mkdir .landfill [root@QA-28 mnt]# echo $? 0 [root@QA-28 mnt]# ls -a . .. [root@QA-28 mnt]# cd .landfill bash: cd: .landfill: No such file or directory [root@QA-28 mnt]# rmdir .landfill rmdir: failed to remove `.landfill': No such file or directory [root@QA-28 mnt]# mkdir .landfill mkdir: cannot create directory `.landfill': File exists [root@QA-28 mnt]# Expected results: Either user's shouldn't be allowed to create .landfill or if allowed it should be accessible.
Created attachment 588168 [details] Test cases for old_trash to new_trash .landfill -> .glusterfs/landfill The issue happens because the .landfill dir is trash dir for AFR. Attached are the test cases for moving it into .glusterfs
Patch present only in master. Not in release-3.3