Hi I just tracked down a SIGSEGV in glusterfsd 3.2.5 due to the failure of checking pthread_mutex_init() return value. Most likely it goe ENOMEM but carried on, and it crashed later on a pthread_mutex_lock() A quick inspection of the latest code shows that none of pthread_*_init is checked for failure. This would be a large change, but it might help a bit getting relevant error reports, as memory shortage would be reported as such, instead of generating random SIGSEGV later. Anyway, the problem suggests glusterfsd runs out of memory. The core file is 236 MB large. I wonder if this could be a memory leak, or if it is a regular usage pattern of glusterfsd to eat that much memory. What reasonable ressource limits should be set for glusterfsd? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@xxxxxxxxxx
