Why would mounting a GFS or GFS2 filesystem hang with "telling LM to withdraw" messages showing in logs on RHEL5 cluster suite?

Issue

• Cannot mount a gfs2 partition
• Server is in a hung state and GFS mount points are not getting mounted after reboot

• Mounting a GFS2 filesystem is hanging and not completing:

  # mount -v /dev/VolGroup00/disk1 /disk1  
  mount: you didn't specify a filesystem type for /dev/gfsvg01/query  
  I will try type gfs2  
  /sbin/mount.gfs2: mount /dev/mapper/VolGroup00-disk1 /disk1  
  /sbin/mount.gfs2: parse_opts: opts = "rw"  
  /sbin/mount.gfs2: clear flag 1 for "rw", flags = 0  
  /sbin/mount.gfs2: parse_opts: flags = 0  
  /sbin/mount.gfs2: parse_opts: extra = ""  
  /sbin/mount.gfs2: parse_opts: hostdata = ""  
  /sbin/mount.gfs2: parse_opts: lockproto = ""  
  /sbin/mount.gfs2: parse_opts: locktable = ""  
  /sbin/mount.gfs2: message to gfs_controld: asking to join mountgroup:  
  /sbin/mount.gfs2: write "join /disk1 gfs2 lock_dlm cluster:disk1 rw /dev/mapper/VolGroup00-disk1"  
  /sbin/mount.gfs2: message from gfs_controld: response to join request:  
  /sbin/mount.gfs2: lock_dlm_join: read "0"  
  /sbin/mount.gfs2: message from gfs_controld: mount options:  
  /sbin/mount.gfs2: lock_dlm_join: read "hostdata=jid=0:id=458753:first=1"  
  /sbin/mount.gfs2: lock_dlm_join: hostdata: "hostdata=jid=0:id=458753:first=1"  
  /sbin/mount.gfs2: lock_dlm_join: extra_plus: "hostdata=jid=0:id=458753:first=1"