Bug 878880

Summary: Temporary file creation location might be different from target of rename
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Vidya Sakar <vinaraya>
Component: gluster-swiftAssignee: Vijay Bellur <vbellur>
Status: CLOSED WORKSFORME QA Contact: Saurabh <saujain>
Severity: low Docs Contact:
Priority: low    
Version: 2.0CC: gluster-bugs, lpabon, mzywusko, perfbz, ppai, pportant, rhs-bugs, rwheeler
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 876660 Environment:
Last Closed: 2014-06-10 09:25: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:
Bug Depends On: 876660    
Bug Blocks:    

Comment 4 Scott Haines 2013-03-08 21:00:12 UTC
Per 03/05 email exchange w/ PM, targeting for Big Bend.

Comment 5 Luis Pabón 2013-07-12 18:47:57 UTC
Is this still an issue for latest RHS2.1?

Comment 6 Luis Pabón 2013-07-17 01:01:28 UTC
RHS 2.0 UFO Bugs are being set to low priority.

Comment 7 Scott Haines 2013-10-01 21:07:08 UTC
Targeting for 3.0.0 (Denali) release.

Comment 8 Nagaprasad Sathyanarayana 2014-05-06 11:43:43 UTC
Dev ack to 3.0 RHS BZs

Comment 10 Prashanth Pai 2014-06-10 09:25:22 UTC
This is no longer a bug an can be closed.

The temp file created by gluster-swift follows Gluster's dot-prefix-dot-suffix naming where the a file named ".thefile.name.9a7aasv" is hashed to the same Gluster node as "thefile.name". This ensures the renaming of a temp file once written does not move it to another Gluster node.

Although I can confirm the above behavior (or feature), I was not able to find any document that points to this in GlusterFS.