Bug 796656
Summary: | running ping_pong on a file from a gluster mount crashed the gluster client | ||||||
---|---|---|---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Shwetha Panduranga <shwetha.h.panduranga> | ||||
Component: | locks | Assignee: | Junaid <junaid> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||
Severity: | urgent | Docs Contact: | |||||
Priority: | high | ||||||
Version: | mainline | CC: | gluster-bugs, redhat.bugs, social, vagarwal, vbellur | ||||
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:33:47 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 817967 | ||||||
Attachments: |
|
Description
Shwetha Panduranga
2012-02-23 12:01:00 UTC
Created attachment 565285 [details]
Attaching client log
CHANGE: http://review.gluster.com/2852 (protocol/client: Calling GF_FREE on memory allocated via GF_CALLOC.) merged in master by Vijay Bellur (vijay) The issue was, a piece of memory allocated via GF_CALLOC was accidently freed using mem_put. Verified the bug on 3.3.0qa38. bug is fixed. I'm running v3.4.2 and ping_pong doesn't run on two nodes with a replicated volume running: ping_pong -rw test 3 any ideas why not? It looks like this bug may not be fixed? It runs on one node, but hangs on the other. Thanks Rich Sounds like standalone issue which should have it's own bug.
> I'm running v3.4.2 and ping_pong doesn't run on two nodes with a replicated
> volume running:
>
> ping_pong -rw test 3
>
> any ideas why not? It looks like this bug may not be fixed?
> It runs on one node, but hangs on the other.
> Thanks
> Rich
|