Bug 852221
Summary: | Crash in fuse_thread_proc on Fedora 17 | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Joe Julian <joe> | |
Component: | fuse | Assignee: | Raghavendra Bhat <rabhat> | |
Status: | CLOSED DEFERRED | QA Contact: | ||
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 3.3.0 | CC: | bfoster, bugs, gluster-bugs, rwheeler | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 852224 (view as bug list) | Environment: | ||
Last Closed: | 2014-12-14 19:40:29 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: | ||||
Bug Depends On: | 856704 | |||
Bug Blocks: |
Description
Joe Julian
2012-08-27 22:02:22 UTC
I confirmed that rolling back to 3.3.7-1.fc16.x86_64 prevents this crash. I just gave 3.3.0 a quick whirl on F17 and didn't reproduce a crash with basic I/O. BTW, my updated F17 is at kernel 3.5.3-1. yumdownloader doesn't give me anything for a 3.5.2-3 kernel... I don't know what operations you're doing to reproduce this, but I can reproduce a crash with an fallocate command (bug 856704). Given the source of this crash (fuse-bridge.c:4072), I suspect this issue could be related. You might want kkeithley's fix from said bug: 2564ab2bc8cd3aa2561e091f72278e480fcef33d doesn't seem to be an issue with latest 3.3 branch, or 3.4.x releases. *** Bug 852224 has been marked as a duplicate of this bug. *** The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug. If there has been no update before 9 December 2014, this bug will get automatocally closed. |