Bug 884280
Summary: | distributed volume - rebalance doesn't finish - getdents stuck in loop | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | S.Knoth <jarl1337> |
Component: | unclassified | Assignee: | Vijay Bellur <vbellur> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | gluster-bugs, sgowda |
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: | 2013-07-25 05:37:38 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
S.Knoth
2012-12-05 19:44:19 UTC
What is the backend fs used? The backend FS is ext4. The recommended backend fs is XFS. Your issue is related to bug 838784. Can you please confirm it? I will mark this as a duplicate of the bug When I run the test program for bug 838784 the output contains 64 bit values which means my system is affected. When I use XFS it seems to work. I'm not sure if that is sufficient to confirm that it's a duplicate of bug 838784. But it is definitely related. I don't understand why it only failed when there were four bricks (2x 100GB 2x 30GB) and worked otherwise. It's a pity that there are problems with glusterfs with ext4 as backend FS. I don't quite understand what the problem is. Isn't it normal that filesystems like ext4 return 64 bit values nowadays, especially on x86_64? Although I don't understand why ext4 returns those crazy numbers as d_off values (but I would guess there is a reason for that). I guess 64 bit values (which can be at least potentially such big numbers) will always bear the risk of overflow, if the dht_itransform function doesn't avoid that in its calculations. And off_t is defined as 64 bit unsigned integer, isn't it? Fixed in 3.3.2 and 3.4.0. |