Description of problem:
while mounting volume using nfs it was hung and found nfs server process was crashed and core was generated. After that killed some brick process and during start force of that volume found crash again
nfs log snippet:-
[2014-08-09 03:25:04.297623] E [nfs.c:341:nfs_init_versions] 0-nfs: Program NLM4 registration failed
[2014-08-09 03:25:04.297642] E [nfs.c:1327:init] 0-nfs: Failed to initialize protocols
[2014-08-09 03:25:04.297654] E [xlator.c:423:xlator_init] 0-nfs-server: Initialization of volume 'nfs-server' failed, review your volfile again
[2014-08-09 03:25:04.297684] E [graph.c:292:glusterfs_graph_init] 0-nfs-server: initializing translator failed
[2014-08-09 03:25:04.297698] E [graph.c:479:glusterfs_graph_activate] 0-graph: init failed
frame : type(0) op(0)
signal received: 11
NLM (of NFS) failed to register with portmapper, so init() routine of NFS xlator returns (-1) to xlator_init(). Call flow:
glusterfsd (NFS process)
xlator_init () => NFS init() routine
But somehow cleanup_and_exit() goes through some race which causes the SEGV. But it clearly says the crash is in the exit code path i.e. NLM failed to register with portmapper and NFS process was about to exit but segfaulted.
The root cause:
The NLM was not able to register with portmapper which prohibited NFS to start.
REVIEW: http://review.gluster.org/9988 (nfs: do not fail to start when optional RPC-programs fail to register) posted (#1) for review on master by Niels de Vos (firstname.lastname@example.org)
REVIEW: http://review.gluster.org/9988 (nfs: do not fail to start when optional RPC-programs fail to register) posted (#2) for review on master by Niels de Vos (email@example.com)
COMMIT: http://review.gluster.org/9988 committed in master by Niels de Vos (firstname.lastname@example.org)
Author: Niels de Vos <email@example.com>
Date: Mon Mar 2 11:14:08 2015 +0100
nfs: do not fail to start when optional RPC-programs fail to register
Some RPC-programs are not strictly required for the NFS-server. When
these optional protocols fail to get registered at the portmapper, there
is no need to fail the starting of the NFS-server.
Tested-by: Brad Hubbard <firstname.lastname@example.org>
Signed-off-by: Niels de Vos <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Kaleb KEITHLEY <email@example.com>
Reviewed-by: jiffin tony Thottan <firstname.lastname@example.org>
Reviewed-by: soumya k <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.
glusterfs-3.7.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.