[Bugs] [Bug 1183340] New: glusterd is non operational due to not implemented getcontext

[bugzilla at redhat.com]

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

            Bug ID: 1183340
           Summary: glusterd is non operational due to not implemented
                    getcontext
           Product: GlusterFS
           Version: 3.4.6
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: p.malishev at gmail.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:

I've compiled gluster for Linux on armv5tel platform which runs Synology NAS.
When I start glusted daemon I have these messages in the log:
--------
[2015-01-18 19:41:34.422649] E [syncop.c:387:synctask_new] 0-syncop: getcontext
failed (Function not implemented)
[2015-01-18 19:41:34.422830] C [glusterd.c:895:glusterd_launch_synctask]
0-management: Failed to spawn bricks and other volume related services
--------
So glusterd is non-operational at all.

The reason why ucontext functions are not implemented is that they have
portability issues and where excluded from POSIX.1-2008.

It would be nice to rework syncop.c to get rid of *context() functions or
provide an alternative, more portable way to manage "threads" (pthreads?) for
such handicapped ARM Linux systems (probably via configure autodetection).


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

GlusterFS v3.4.6
Linux sandra 2.6.32.12 #5022 Wed Jan 7 14:19:44 CST 2015 armv5tel GNU/Linux
synology_88f6281_411j
Glibc 2.15

How reproducible:
Always

Steps to Reproduce:
1. Compile glusterfs
2. Run glusterd
3. Check glusterd's logs

Actual results:
Glusterd does not respond to any cli command, does not respond to 'peer probe'
command from the running cluster

Expected results:
Glusterd is operational

Additional info:

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