On 07/25/2011 06:48 AM, carlopmart wrote: > On 07/25/2011 03:44 PM, Steven Dake wrote: >> On 07/25/2011 05:38 AM, carlopmart wrote: >>> On 06/24/2011 06:06 PM, Nicolas Ross wrote: >>>> >>>>> Thanks for that, that'll prevent me from modifying a system file... >>>>> >>>>> And yes, I find it a little disapointing. We're now at 6.1, and our >>>>> setup is exactly what RHCS was designed for... A GFS over fiber, httpd >>>>> running content from that gfs... >>>> >>>> Two thing I need to mention in this issue. One, support doesn't think >>>> anymore that it's a coro-sync specific issue, they are searching to a >>>> driver issue or other source for this problem. >>>> >>>> Second, I downgraded my kernel to 2.6.32-71.29.1.el6 (pre-6.1, or 6.0), >>>> for another issue, and since I did, I don't think I saw that issue >>>> again. I saw spikes in my cpu graphs, but I'm not 100% sure that they >>>> are caused by this issue. >>>> >>>> So, as a temporary work-around for this time, woule be (at your own >>>> risks) to downgrade to 2.6.32-71.29.1.el6 kernel : >>>> >>>> yum install kernel-2.6.32-71.29.1.el6.x86_64 >>>> >>>> Regards, >>> >>> Hi Steven and Nicolas, >>> >>> Is this bug resolved in RHEL6.1 with all updates applied?? Do I >>> need to >>> use some specific kernel version 2.6.32-131.2.1 or 2.6.32-131.6.1? >>> >>> Thanks. >>> >> >> the corosync portion is going through QE. The kernel portion remains >> open. >> >> Regards >> -steve >> > > Thanks Steve, then, Can I use last corosync version provided with > RHEL6.1 and last RHEL6.0's kernel version without problems?? > > > I recommend not mixing without a support signoff. Regards -steve -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
