If gulm or cmam use anything other than the value of uname -n for the cluster nodename, gnbd will be using the wrong name. This means that gnbd will not be able to correctly fence the server. Also, unless the nodename parameter for fence_gnbd is equal to uname -n, fence_gnbd will return false successes, allowing corruption to occur.
I changed the default behaviour of gnbd to get the nodename from magma. If gnbd is being used for some non-clustered purpose, the magma check can be overriden by using the -n option to gnbd_import or gnbd_serv. When -n is used, gnbd will simply use uname -n.