Bug 765583 (GLUSTER-3851) - Rebalance fails to rebalance files whose name length is close to the filesystem's limit
Summary: Rebalance fails to rebalance files whose name length is close to the filesyst...
Keywords:
Status: CLOSED UPSTREAM
Alias: GLUSTER-3851
Product: GlusterFS
Classification: Community
Component: distribute
Version: 3.2.5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: shishir gowda
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-07 15:42 UTC by Pierre-Francois Laquerre
Modified: 2013-12-09 01:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-18 05:58:39 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Pierre-Francois Laquerre 2011-12-07 15:42:30 UTC
When rebalancing a file, gluster creates a copy with the name ".$filename.gfs$filesize", e.g. ".foo.gfs3" for a 3 byte file named "foo". If the length of the file name is very close to the filesystem's limit (255 bytes in the case of ext3), then this operation will fail:

[snippet from the rebalance log]
> [2011-12-07 07:53:32.607413] W [fuse-bridge.c:184:fuse_entry_cbk] 0-glusterfs-fuse: 323262192: LOOKUP() /path/to/.somereallyreallyreallystupidlylongfilename.gfs40200 => -1 (File name too long)
> [2011-12-07 07:53:58.321882] E [client3_1-fops.c:2228:client3_1_lookup_cbk] 1-volname-client-1: remote operation failed: File name too long

Comment 1 shishir gowda 2012-04-18 05:58:39 UTC
This bug is fixed in the upstream.
Please upgrade to release 3.3beta2.


Note You need to log in before you can comment on or make changes to this bug.