[Bugs] [Bug 1774711] New: vm paused by io-error, crashed on resume, gf_thread_vcreate errors in logs

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1774711

            Bug ID: 1774711
           Summary: vm paused by io-error, crashed on resume,
                    gf_thread_vcreate errors in logs
           Product: GlusterFS
           Version: 6
          Hardware: x86_64
                OS: Linux
            Status: NEW
         Component: io-threads
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: budic at onholyground.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



Created attachment 1638202
  --> https://bugzilla.redhat.com/attachment.cgi?id=1638202&action=edit
libvirtd log for affected VM

Description of problem: vm locked up on io to gluster volume using libgfapi
mounts in ovirt. Crashed when attempting to resume. Interestingly, this seems
to happen approximately every 10 days on one volume.

[2019-11-20 17:48:42.189605] E [MSGID: 101072]
[common-utils.c:4030:gf_thread_vc
reate] 0-gDBv2-io-threads: Thread creation failed [Resource temporarily
unavaila
ble]


Version-Release number of selected component (if applicable):
Gluster 6, various versions, latest from 6.6

How reproducible:
has been repeating approximately every 10 days since upgrading to Gluster 6

Steps to Reproduce:
1. start vm
2. wait ~10 days
3. vm crashes

Actual results:
vm locks up and crashes when attempting to resume

Expected results:
vm does not lock up using gluster volume

Additional info:
This particular volume hosts a RRD database for Observium using rrd-daemon, so
there is a heavy write load every 30 minutes. Volume had
performance.io-thread-count = 32 when it crashed, just turned it up to 64 as a
test.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.