Bug 1693184
Summary: | A brick process(glusterfsd) died with 'memory violation' | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | JeongKinam <knjeong> |
Component: | replicate | Assignee: | Ravishankar N <ravishankar> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | experimental | CC: | atumball, bugs |
Target Milestone: | --- | ||
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: | 2019-08-05 10:00: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
JeongKinam
2019-03-27 10:01:49 UTC
> I'm using a volume with two replicas of the 3.6.9 version of GlusterFS.
Is it possible to upgrade version of glusterfs? Current glusterfs versions are at least 2+ years from that version, and we have fixed a **lot** of memory violation errors (coverity/clang-scan etc).
We had not seen any issues similar to this strace in a long time. Let us know how the upgrade goes, and ping us if you need help with any upgrade issues.
Hi Jeong, I'm closing this bug as gluster 3.6 was EOL'd long back. Please feel free to re-open the bug if issue persists in any of the current supported releases. |