Bug 1383597
| Summary: | Crash when drive became full | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Pavel Černohorský <pavel.cernohorsky> |
| Component: | write-behind | Assignee: | Csaba Henk <csaba> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.8 | CC: | bugs, mliyazud, ndevos, pavel.cernohorsky, rgowdapp |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-09-06 12:00:21 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
Pavel Černohorský
2016-10-11 07:54:02 UTC
Raghavenda, have you seen something like this before? (In reply to Niels de Vos from comment #1) > Raghavenda, have you seen something like this before? Its difficult to say as bt doesn't involve any symbols. Logs after installing gluster debuginfo packages or a bt through gdb would've helped. Is it possible to get them? However there are some fixes to write-behind that might've fixed memory corruptions (though not sure whether this bug is same issue): https://review.gluster.org/16464 (In reply to Raghavendra G from comment #2) > (In reply to Niels de Vos from comment #1) > > Raghavenda, have you seen something like this before? > > Its difficult to say as bt doesn't involve any symbols. Logs after > installing gluster debuginfo packages or a bt through gdb would've helped. > Is it possible to get them? However there are some fixes to write-behind > that might've fixed memory corruptions (though not sure whether this bug is > same issue): > https://review.gluster.org/16464 Looking at the bug title, this patch could be related as it fixes a memory corruption in the code-path where we encounter short writes. (In reply to Raghavendra G from comment #3) > (In reply to Raghavendra G from comment #2) > > (In reply to Niels de Vos from comment #1) > > > Raghavenda, have you seen something like this before? > > > > Its difficult to say as bt doesn't involve any symbols. Logs after > > installing gluster debuginfo packages or a bt through gdb would've helped. > > Is it possible to get them? However there are some fixes to write-behind > > that might've fixed memory corruptions (though not sure whether this bug is > > same issue): > > https://review.gluster.org/16464 > > Looking at the bug title, this patch could be related as it fixes a memory > corruption in the code-path where we encounter short writes. Unfortunately we do not have the setup with that version and type of load any more (we have moved away from Gluster for that usecase because we had much more problems and unstabilities as well), so I cannot provide you with more information. As for whether the above mentioned patch set solves the problem, I afraid that without reading a lot of code there I cannot easily say. I believe in your expertise and professional experience based feeling:) Closing as setup exhibiting the issue has been decommissioned. |