[Bugs] [Bug 1226307] New: Volume start fails when glusterfs is source compiled with GCC v5.1.1

bugzilla at redhat.com bugzilla at redhat.com
Fri May 29 12:13:53 UTC 2015


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

            Bug ID: 1226307
           Summary: Volume start fails when glusterfs is source compiled
                    with GCC v5.1.1
           Product: GlusterFS
           Version: mainline
         Component: geo-replication
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: achiraya at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
When GlusterFS [master] is compiled and built on a fedora 22 machine with GCC
v5.1.1, volume start fails with the following error in brick logs

[2015-05-28 07:12:42.176108] I [event-epoll.c:629:event_dispatch_epoll_worker]
0-epoll: Started thread with index 1
[2015-05-28 07:12:42.178705] W [xlator.c:192:xlator_dynload] 0-xlator:
/usr/local/lib/glusterfs/3.8dev/xlator/features/changelog.so: undefined symbol:
changelog_select_event
[2015-05-28 07:12:42.178721] E [graph.y:212:volume_type] 0-parser: Volume
'patchy-changelog', line 30: type 'features/changelog' is not valid or not
found on this machine
[2015-05-28 07:12:42.178733] E [graph.y:321:volume_end] 0-parser: "type" not
specified for volume patchy-changelog
[2015-05-28 07:12:42.178850] E [MSGID: 100026]
[glusterfsd.c:2149:glusterfs_process_volfp] 0-: failed to construct the graph
[2015-05-28 07:12:42.178974] W [glusterfsd.c:1219:cleanup_and_exit] (--> 0-:
received signum (0), shutting down

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

GlusterFS (master) on fedora22 with GCC v5.1.1

How reproducible:
Always

Steps to Reproduce:
1. git clone master from review.gluster.org
2. Compile and install
3. Create a simple distributed volume
4. Start the volume

Actual results:
Volume start failed.

Expected results:
Volume start should be successful

Additional info:

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


More information about the Bugs mailing list