Bug 1471963
| Summary: | Glusterfind : Move Operations performed in the Filesystem are not reported correctly | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Bhupeshraj <bhupeshrajs> |
| Component: | glusterfind | Assignee: | bugs <bugs> |
| Status: | CLOSED EOL | QA Contact: | bugs <bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.10 | CC: | avishwan, bhupeshrajs, bugs, khiremat |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-06-20 18:28:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained. As a result this bug is being closed. If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately. |
Description of problem: Move operations performed in the Filesystem are not reported correctly by the glusterfind query API. Version-Release number of selected component (if applicable): 3.10.3 How reproducible: 100% (also in earlier version 3.7.12) Steps to Reproduce: 1. Create Folders using mkdir -p dir1/dir2/dir3 at mount point 2. Note the time after creating the folders in Step 1 as t1. 3. Execute the following move commands : mv dir1/dir2/dir3 dir3 mv dir1 dir3 4. The current directory structure is dir3/dir1/dir2 5. Execute glusterfind query volume-name outfile --since-time=t1 . i.e Find the incremental changes that happened after Step 1. Actual results: The glusterfind query returned : RENAME dir3/dir1/dir2/dir3 dir3 RENAME dir1 dir3/dir1 Expected results: The first result of the glusterfind query should be RENAME dir1/dir2/dir3 dir3 Additional info: The same error can be seen in different move cases: Consider the following directory structure: Folder1\ File1.txt Folder2\ Note the time as t2. Perform the following move/rename operations mv Folder1/File1.txt Folder1/File2.txt mv Folder1/ Folder2/ Executing the glusterfind query command using --since-time=t2 yields the following results RENAME Folder2/Folder1/File1.txt Folder2/Folder1/File2.txt RENAME Folder1 Folder2/Folder1 The first result is wrong. The expected first result should be RENAME Folder1/File1.txt Folder1/File2.txt