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:
Do know of a similar distro that doesn't have *context() functions that runs on something like a beagleboard xM or Raspberry Pi?
Unfortunately, I'm not aware of such distros. But I've never studied distros for ucontext support.
GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5. This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs". If there is no response by the end of the month, this bug will get automatically closed.
It is still there in 3.5.3
This bug is getting closed because the 3.5 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.