Bug 764855 (GLUSTER-3123)
Summary: | [a7cdaf3de307c96cb55219a0743962ee1e1fc955]: glusterd crashed when started | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Raghavendra Bhat <rabhat> |
Component: | glusterd | Assignee: | Raghavendra Bhat <rabhat> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | mainline | CC: | gluster-bugs, lakshmipathi |
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: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Raghavendra Bhat
2011-07-04 07:51:23 UTC
Raghavendra Bhat has sent a patch for this. That should fix the crash. I am keeping this bug so I can figure out the root cause why it was written as '0' in first place. PATCH: http://patches.gluster.com/patch/7743 in master (glusterd: check replica_count for 0 before using it for volume creation in stripe replicate volume) Now is fixed since we are checking volinfo->replica_count for zero before assigning it to sub_count and performing the division operation. |