Bug 860140

Summary: Error when renaming a file, and while enabling/disabling performance translators
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: glusterfsAssignee: Raghavendra G <rgowdapp>
Status: CLOSED DUPLICATE QA Contact: Sudhir D <sdharane>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0CC: amarts, rhs-bugs, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-11 09:40:16 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:

Description SATHEESARAN 2012-09-25 05:19:15 UTC
Description of problem:
While renaming the file continuously(from 'oldname' to 'newname' and vice versa), and disabling any of performance translators, throws errors[ mv: cannot move 'oldfile' to 'newfile' :No such file or directory  OR 'oldfile' and 'newfile' are the same file]

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

How reproducible:
Consistent

Steps to Reproduce:
1. Rename the file continuously in a loop [mv 'oldfile' 'newfile']
2. Try to disable/enable performance translators(stat-prefetch,quick-read,io-cache,read-ahead,write-behind) through volume set option

  
Actual results:
1. Getting errors while renaming a file[mv: cannot move 'oldfile' to 'newfile' :No such file or directory  OR 'oldfile' and 'newfile' are the same file]

NOTE: this error was transient, after sometime renaming continues without error

Expected results:
There should not be any errors in renaming a files

Additional info:

Comment 2 Amar Tumballi 2012-09-26 05:07:33 UTC
Du, is it same as the rename issue with fuse resolve? (the parents' graph differ).

Comment 3 Amar Tumballi 2012-10-11 09:40:16 UTC
same as bug 804592

*** This bug has been marked as a duplicate of bug 804592 ***