+++ This bug was initially created as a clone of Bug #1283509 +++ Description of problem: If we expand a new brick to a WORM volume and create some new files, the files located in the new brick can be renamed. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. create a dht volume and enable WORM feature 2. add one brick to the volume 3. fix layout of the volume 4. create some files in the client directory 5. rename files which are located in the new added brick Actual results: Mv operation succeeds without any error reported. But the new name and the original name both exists. Expected results: Mv operation is not allowed. 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.