Bug 859162
Summary: | FUSE client crashes | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Louis Zuckerman <glusterbugs> |
Component: | core | Assignee: | Raghavendra Bhat <rabhat> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | medium | ||
Version: | 3.1.7 | CC: | amarts, gluster-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-11-30 18:05:20 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
Louis Zuckerman
2012-09-20 17:08:30 UTC
Here is the volume info for this volume... Volume Name: builder Type: Replicate Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: server1:/bricks/builder0 Brick2: server2:/bricks/builder0 Options Reconfigured: diagnostics.client-log-level: INFO And here is a sample line from both of the brick logs on the servers, they produce a bunch of lines like this right before the client crashes... [2012-09-20 05:03:04.976830] I [server-helpers.c:459:do_fd_cleanup] 0-builder-server: fd cleanup on /nexus/sonatype-work/nexus/timeline/index/_3pi.prx 3.1.7? any chance of at least upgrading to 3.2.x series at the least? Meantime, will try to figure out the issue in release-3.1 branch The client made it through the night without crashing yesterday. And yes, I will work on upgrading to 3.2. I was hoping someone would see that stacktrace or log & recognize an obvious problem, because I do not think this will be easy to reproduce. I have lots of clients, many with uptimes of monthsm, and have almost never seen any crash. I was able to reproduce the crash again this afternoon since my last comment. This volume stores SVN repos & a Nexus maven repository, among other things. When I tried doing a build which checked out from SVN and Nexus the mount crashed. This explains the nightly crashes, they happened when Jenkins would run the nightly builds. Joe Julian suggested (in IRC) that I try stopping & starting the volume. I did that, and also rebooted the client machine, and now everything seems to be working fine -- I am able to do the Jenkins builds without the client crashing. This whole problem seemed to be caused by a rolling reboot of the servers for this volume. I have done this many times in the past with this volume and other volumes and never ran into this kind of trouble. In any case, it seems to be resolved now since I stopped & restarted the volume. moving the priority down as workaround exists, and also because the version is 3.1.x which is not *actively* looked into. Louis, does that sound ok for you? Yes that is fine with me. I have not seen this bug happen again since I reported it. My volumes have been very stable. Thanks! WORKSFORME with latest release then. Please upgrade to 3.3.x (or at least 3.2.x), don't remain in 3.1.x releases |