commit ac07c1e11e5a732ec80c5731f91307667a36ca31
Author: Bob Peterson <rpeterso@redhat.com>
Date:   Tue Mar 9 09:05:40 2010 -0600

    cman: gfs_controld dm suspend hangs withdrawn GFS file system
    
    This patch changes gfs_controld such that if a device mapper (dm)
    suspend needs to be done, it passes the --nolockfs and --noflush
    parameters.  Now that gfs and gfs2 are using the standard means
    of calling freeze and thaw, a gfs withdraw will cause the
    suspend uevent.  Without those parameters, the file system is
    permanently frozen with no way to unfreeze.  (You can't unfreeze
    it since gfs has withdrawn).  In other words, a reboot of the
    entire cluster it required to recover.
    
    rhbz#570530

diff --git a/group/gfs_controld/recover.c b/group/gfs_controld/recover.c
index 3eec64f..931b357 100644
--- a/group/gfs_controld/recover.c
+++ b/group/gfs_controld/recover.c
@@ -2711,7 +2711,8 @@ static int run_dmsetup_suspend(struct mountgroup *mg, char *dev)
 		for (i = 0; i < 50; i++)
 			close(i);
 	
-		execlp("dmsetup", "dmsetup", "suspend", buf, NULL);
+		execlp("dmsetup", "dmsetup", "suspend",  "--nolockfs",
+		       "--noflush", buf, NULL);
 		exit(EXIT_FAILURE);
 	}
 	return -1;