+++ This bug was initially created as a clone of Bug #1214561 +++ Description of problem: Glusterfind API presently is just able to mention the files which have been newly created, or have had data/metadata changes. In case a file is deleted, it is not able to get that information from the changelog file This bug is to track the progress made on that front. Version-Release number of selected component (if applicable): Glusterfs 3.7 upstream How reproducible: Always Steps to Reproduce: 1. Have a gluster volume of type distribute/replicate 2. Create 2 files 'file1' and 'file2' 3. Edit the contents of 'file2' 4. Delete 'file2' 5. Change the permissions of 'file1' to (say) read-only 6. Verify the contents of changelog file. Actual results: Step 6 should shows Entry operations for 'file1' and 'file2', followed with Data operation for 'file2', and a Metadata operation for 'file1' Delete operation of 'file2' (step4) is not recorded in the changelog file. Expected results: Delete operation of 'file2' should get recorded in the changelog file, which in turn can be used by Glusterfind.
REVIEW: http://review.gluster.org/10500 (geo-rep: Changes required as part of changelog version 1.2) posted (#1) for review on release-3.7 by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/10500 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit 4e576b97f0c5b636f2e6490371408ebc18c97f6d Author: Kotresh HR <khiremat> Date: Thu Apr 23 10:18:49 2015 +0530 geo-rep: Changes required as part of changelog version 1.2 The index value for UNLINK and RMDIR in changelog is no more the last index. It varies based on whether the 'changelog.capture-del-path' is enabled or not. Hence, fixed index is used. The option to capture deleted path in changelog comes with the patch: http://review.gluster.org/#/c/10288/ And the parser changes with http://review.gluster.org/#/c/10166/ BUG: 1217935 Change-Id: I6d8a941129416381e24226faed9803f7e5fae8d0 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/10344 Reviewed-on: http://review.gluster.org/10500 Tested-by: NetBSD Build System Reviewed-by: Aravinda VK <avishwan> Tested-by: Gluster Build System <jenkins.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user