The cluster log server can seg fault. This means that the kernel can no longer communicate with userspace and get any work done.
If a mirror was started and then suspended very shortly after, the list of pent-up requests waiting for a checkpoint would be freed. If one of those requests was POSTSUSPEND, it would be processed and would also try to free the list of pent-up requests. Since this action was nested, the outer function would segfault because the list it was processing was free out from under it. commit c9d6207f212f900f66c9c6990462bae328ede121 Author: Jonathan Brassow <jbrassow> Date: Tue Feb 10 16:11:43 2009 -0600
I have not seen any seg faults with the latest rpms, marking verified. 2.6.18-150.el5 lvm2-2.02.46-5.el5 BUILT: Sat Jun 6 16:29:23 CDT 2009 lvm2-cluster-2.02.46-5.el5 BUILT: Sat Jun 6 16:28:13 CDT 2009 device-mapper-1.02.32-1.el5 BUILT: Thu May 21 02:18:23 CDT 2009 cmirror-1.1.37-1.el5 BUILT: Tue May 5 11:46:05 CDT 2009 kmod-cmirror-0.1.21-14.el5 BUILT: Thu May 21 08:28:17 CDT 2009
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/RHEA-2009-1340.html