Bug 762696 (GLUSTER-964)

Summary: rename to .landfill might fail due to file name too long
Product: [Community] GlusterFS Reporter: Vikas Gorur <vikas>
Component: replicateAssignee: Anand Avati <aavati>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: mainlineCC: amarts, chrisw, gluster-bugs, vijay
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Vikas Gorur 2010-05-27 19:59:27 UTC 
When entry self heal needs to delete a file or directory, for atomicity it renames it to .landfill/path. Here the path is derived from the original pathname by replacing "/" with "-". However, this can result in a basename that is longer than 256 characters, causing the rename to fail with ENAMETOOLONG.

The fix is to rename to a basename that is a textual representation of the MD5 hash of the original pathname.