Bug 1236282

Description of problem:
When a file is moved from its original location to another directory, with the same name or with a different name, the change does not get captured in the output file. File rename at the same location does not get recorded as well. 

Do note that this issue is seen intermittently in a replica 3 volume.

However on a replica 2 volume, every file movement (across directories) gets recorded as a MODIFY entry and a rename (also) gets recorded as a MODIFY entry (bug 1227691)

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. Create a replica 3 volume 'cross3' and a glusterfind session
2. Mount the volume over nfs/fuse and create 2 files 'test1' and 'test2' and a directory 'dir1'
3. Execute glusterfind pre and verify that 3 NEW entries are seen in the output file
4. Move the file 'test1' to dir1/test1 and run glusterfind pre and post
5. Output file shows a MODIFY entry for dir1/test1
6. Rename the file 'test2' to 'newtest2' and run glusterfind pre and post
7. Output file remains empty, without logging in any change
8. Move the file 'dir1/test1' to its original location, this time with a change in name. Run glusterfind pre and post
9. Output file again remains empty.

REVIEW: http://review.gluster.org/11444 (tools/glusterfind: RENAME and MODIFY issues) posted (#1) for review on release-3.7 by Kotresh HR (khiremat)

REVIEW: http://review.gluster.org/11444 (tools/glusterfind: RENAME and MODIFY issues) posted (#2) for review on release-3.7 by Kotresh HR (khiremat)

REVIEW: http://review.gluster.org/11444 (tools/glusterfind: RENAME and MODIFY issues) posted (#3) for review on release-3.7 by Kotresh HR (khiremat)

COMMIT: http://review.gluster.org/11548 committed in release-3.7 by Venky Shankar (vshankar) 
------
commit 8a210d46424c2c7a20a9e8a94b0a4719df7cb8c7
Author: Aravinda VK <avishwan>
Date:   Fri Jun 26 22:36:31 2015 -0400

    tools/glusterfind: RENAME and MODIFY issues
    
    If Modification happens before RENAME, GFID to Path Conversion
    converts it into New Path. Delete Modify Entry and insert again
    So that MODIFY <NEW NAME> comes after RENAME.
    
    Default value of pgfids and basenames changed to "" instead of NULL
    Also fixed RENAME issue of displaying "RENAME <NEW NAME> <NEW NAME>".
    Also fixed RENAME followed by missing MODIFY
    
    Change-Id: I8202f6e6ec33f7bd921e71da38677f2ee2dab87a
    BUG: 1236282
    Signed-off-by: Kotresh HR <khiremat>
    Signed-off-by: Milind Changire <mchangir>
    Reviewed-on: http://review.gluster.org/11443
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Aravinda VK <avishwan>
    Tested-by: NetBSD Build System <jenkins.org>
    (cherry picked from commit adc704557a141a624fc702f7303b8b81582e1598)
    Reviewed-on: http://review.gluster.org/11548
    Reviewed-by: Venky Shankar <vshankar>

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.3, please open a new bug report.

glusterfs-3.7.3 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/12078
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user