Description of problem: RFE: Currently the debug options seems to be the only way to cause the system to panic on a GFS error. The scenario I am testing is when a cluster node loses all access to storage. Currently it withraws, but to ensure the system is fenced the debug option can cause it to panic. Version-Release number of selected component (if applicable): 5.2 gfs-utils-0.1.17-1.el5 How reproducible: Everytime Steps to Reproduce: 1. Setup GFS 2. Remove all storage access from a node 3. System withdraws GFS, but stays operational in the cluster Actual results: If the node is running services, and cluster communications are working fine, and the services do not fail over. Adding "debug" to the mount option allows the system to panic instead. This causes it to fence, and everything else falls into place. Expected results: If a system loses access to the storage and thus GFS, it should not remain operational in the cluster. An option to panic the node on any GFS errors as documented in the mount man page for other filesystems would be nice. This ensures the system is fenced and services fail over.
We should probably consider doing this in GFS2 first, and the maybe back port to GFS.
Now that we've decided how to handle bug #488499, and have a working prototype patch for it, it clearly implements the RFE in this bugzilla. So I'm closing this bug as a duplicate of that one. *** This bug has been marked as a duplicate of bug 488499 ***