| Summary: | Start and stop glusterd fails to start a previously created volume | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Harshavardhana <fharshav> |
| Component: | glusterd | Assignee: | Pranith Kumar K <pkarampu> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 3.1.0 | CC: | cww, gluster-bugs, vijay |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| 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: | |
|
Description
Harshavardhana
2010-10-11 23:50:55 UTC
This bug is the result of not raising errors when retrieving the glusterd-store for the brick is corrupted. Ideally if there are errors in retrieving the glusterd-store, glusterd should exit giving the error, which is done as part of 2066. This corruption happened because of the bugs in glusterd-store which is fixed as part of 1754. So closing this bug |