+++ This bug was initially created as a clone of Bug #1228597 +++ Description of problem: Have a volume and glusterfind session(s) created for the same. When any metadata changes are done to any file, it gets captured in teh output file. However, when the owner/group of a directory is changed, there is no metion of the same in the output file. Version-Release number of selected component (if applicable): glusterfs-3.7.0-3.el6rhs.x86_64 How reproducible: Always Steps to Reproduce: 1. Have a volume 2*2 'testvol' and glusterfind sessions 'sess1' and 'sess2' 2. Mount it over nfs/fuse and create 2 files and a directory 'dir1' 3. Change the permissions, owner, group of a file and run glusterfind pre and post 4. Verify that the file has a mention in the output file with the type MODIFY 5. Do the same for 'dir1' and execute glusterfind pre and post Actual results: Step5 generates an output file which does not have a mention of MODIFY op for the directory Expected results: Metadata changes to directory should get logged in the output file
REVIEW: http://review.gluster.org/11158 (tools/glusterfind: Fix GFID to Path conversion for dir) posted (#2) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/11158 (tools/glusterfind: Fix GFID to Path conversion for dir) posted (#3) for review on master by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/11158 committed in master by Vijay Bellur (vbellur) ------ commit 076e869c65dbe2ef9fa34b05756d23849ae4e852 Author: Aravinda VK <avishwan> Date: Wed Jun 10 15:26:47 2015 +0530 tools/glusterfind: Fix GFID to Path conversion for dir For Directories, GFID to Path conversion was fine, but wrong filter was used while updating to db. Change-Id: Id588adbb25ff5fd357f8cc2d5485bd2eb4a52b65 Signed-off-by: Aravinda VK <avishwan> BUG: 1230127 Reviewed-on: http://review.gluster.org/11158 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kotresh HR <khiremat> Reviewed-by: Vijay Bellur <vbellur>
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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user