Bug 762696 (GLUSTER-964) - rename to .landfill might fail due to file name too long
Summary: rename to .landfill might fail due to file name too long
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-964
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: All
OS: All
low
medium
Target Milestone: ---
Assignee: Anand Avati
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-27 19:59 UTC by Vikas Gorur
Modified: 2015-12-01 16:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.