+++ This bug was initially created as a clone of Bug #517145 +++ which was itself a clone of Bug #488499 +++ This bug will be used to add the mount options "-o errors=panic" and "-o errors=withdraw" for mounting GFS2 file systems. If "-o errors" is not specified or if "errors=withdraw" is specified, GFS2 file system errors will be treated as they are today. That is, if the error is not severe, the file system will simply "withdraw" and the file system will become unusable until the system is rebooted. What happens next depends on the value of the "kernel.panic_on_oops" sysctl value. The default behavior for the kernel is to panic when the oops occurs. If the users have overridden this with "sysctl -w kernel.panic_on_oops=0" the system will keep running after the file system withdraw occurs. If "-o errors=panic" is specified, even non-severe file system errors will cause the system to force a kernel panic. This may be useful (when combined with other options) for automatically rebooting a system with errors when a fencing device is used that does not force a reboot (fabric-level fencing, such as fence_scsi).
Bob, is there anything preventing posting the patch for this bz now?
Nope, I've just got to take time to do it.
Created attachment 363520 [details] Patch to fix the problem The crosswrite patch appears upstream. This is the patch I POSTed for inclusion into 5.5. It was tested on system roth-01.
in kernel-2.6.18-168.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 Please do NOT transition this bugzilla state to VERIFIED until our QE team has sent specific instructions indicating when to do so. However feel free to provide a comment indicating that this fix has been verified.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: This patch introduces GFS2 support for the errors= mount command line option. This is similar in intent to the ext3 option of the same name, although currently there are only two supported options. The default, errors=withdraw results in the filesystem attempting to withdraw from the cluster if an I/O error or metadata error is encountered. The alternative, errors=panic results in a panic in the same situation. This can be useful during certain kinds of testing.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0178.html