[Bugs] [Bug 1535526] New: glusterfind : wrong results while retrieving incremental list of files modified after last run

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1535526

            Bug ID: 1535526
           Summary: glusterfind : wrong results while retrieving
                    incremental list of files modified after last run
           Product: GlusterFS
           Version: 3.10
         Component: glusterfind
          Assignee: bugs at gluster.org
          Reporter: bhupeshrajs at gmail.com
        QA Contact: bugs at gluster.org
                CC: avishwan at redhat.com, bugs at gluster.org,
                    khiremat at redhat.com



Description of problem: glusterfind : wrong results while retrieving
incremental list of files modified after last run

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


How reproducible: 100%


Steps to Reproduce:

1. Consider we have a folder in gluster volume 

Folder1/
       File1.txt
       File2.txt


Note current time as t1.


2. Now perform these operations : 

    Create a New Folder Folder2 with files File3.txt and File4.txt.
    Delete Folder1
    Rename Folder2 to Folder1.

    Now gluster volume will contain :

    Folder1/
           File3.txt
           File4.txt

3. Perform glusterfind query --since-time=t1 glustervolume output.txt


Actual results:

NEW /mnt/glusterfs/Folder1
NEW /mnt/glusterfs/Folder1/File3.txt
NEW /mnt/glusterfs/Folder1/File4.txt
DELETE /mnt/glusterfs/Folder1/File1.txt
DELETE /mnt/glusterfs/Folder1/File2.txt
DELETE /mnt/glusterfs/Folder1

Expected results:

NEW /mnt/glusterfs/Folder1/File3.txt
NEW /mnt/glusterfs/Folder1/File4.txt
DELETE /mnt/glusterfs/Folder1/File1.txt
DELETE /mnt/glusterfs/Folder1/File2.txt

Or

DELETE /mnt/glusterfs/Folder1/File1.txt
DELETE /mnt/glusterfs/Folder1/File2.txt
DELETE /mnt/glusterfs/Folder1
NEW /mnt/glusterfs/Folder1
NEW /mnt/glusterfs/Folder1/File3.txt
NEW /mnt/glusterfs/Folder1/File4.txt

Additional info : This is reproducible 100 %

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.