[Bugs] [Bug 1665216] New: Databases crashes on Gluster 5 with the option performance.write-behind enabled

[bugzilla at redhat.com]

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

            Bug ID: 1665216
           Summary: Databases crashes on Gluster 5 with the option
                    performance.write-behind enabled
           Product: GlusterFS
           Version: 5
          Hardware: x86_64
                OS: Linux
            Status: NEW
         Component: core
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: gabisoft at freesurf.ch
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



Created attachment 1519880
  --> https://bugzilla.redhat.com/attachment.cgi?id=1519880&action=edit
asb-etcd-1-smjcf.log

Description of problem:
Running Etcd, Cassandra and PostgreSQL show a stacktrace after starting with DB
files on Gluster 5.2 volumes, if the volume has enabled the volume option
performance.write-behind. Using the Gluster volumes to serve normal files does
not enforce the issue.

Version-Release number of selected component (if applicable):
5.2


How reproducible:


Steps to Reproduce:
1. Start Etcd with DB files on a gluster volume option performance.write-behind
is on
2. Etcd does start and crashes after listening to clients (unexpected fault
address 0x7fca0c001040)
3. Disable performance.write-behind on the gluster volume
4. Restart Etcd
5. Etcd does start normally

Actual results:
Output of a Etcd crashing (asb-etcd-1-smjcf.log)

Expected results:
Output of a Etcd running with performance.write-behind off
(asb-etcd-3-dsfxf.log)


Additional info:
The content or size of the Etcd DB doesn't matter. It is also reproducible if
the DB is created from scratch.

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