Bug 796171
Summary: | [2b52b096a7db3124fdd97554e63792f36e889af9]: Source brick crashed with core when replace-brick is issued. | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Rahul C S <rahulcs> |
Component: | glusterd | Assignee: | krishnan parthasarathi <kparthas> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | pre-release | CC: | gluster-bugs, nsathyan, rfortier |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.4.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-24 17:30:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | 1f3a0dd4742a2fcd3215aee4a5e22125d7ea4f4d | Category: | --- |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 817967 |
Description
Rahul C S
2012-02-22 12:30:17 UTC
The issue is that index xlator needs a resolved inode in the incoming xattrop request to perform its indexing. In the case of replace-brick pump xlator, unlike server doesn't resolve inode, leading to null gfid sent to index xlator. Positioning pump above index xlator in the graph avoids this problem in the first place. This solution is justified since pump as opposed to afr doesn't 'need' the services of index xlator. CHANGE: http://review.gluster.com/2801 (glusterd: Modified server graph to have index xl above pump) merged in master by Vijay Bellur (vijay) Not finding the crash with same procedure. replace-brick happening properly according to status. |