On Thu, May 15, 2008 at 08:13:59AM -0700, Collins, Kevin [Beeline] wrote:
> Well, here is the final outcome:
>
> This is a bug in RHEL5 and RHEL4, and will be fixed in RHEL5u2, which is
> likely to be released in the the next 2 weeks or so, and RHEL4u7.
>
> As a workaround, you can kill and restart clvmd on all nodes (as opposed
> to the "service" clvmd) while there are no LVM changes being made *this
> may cause problems - no serious testing was done*.
>
> Optionally, you could probably open a ticket and request an
> "unsupported" patch, which is what I currently have...
> (device-mapper-1.02.24-1.el5.i386.rpm
> lvm2-cluster-2.02.32-4.el5.i386.rpm lvm2-2.02.32-1.el5.i386.rpm)
>
> Here are the bug IDs I was given:
>
> RHEL5:
> https://bugzilla.redhat.com/show_bug.cgi?id=437446
>
> RHEL4:
> https://bugzilla.redhat.com/show_bug.cgi?id=435341
>
> Hope this helps... Also crossposting to the RHEL4 list.
>

Hi!

Is it working now with RHEL5u2 ?

Just curious :)

-- Pasi

_______________________________________________
rhelv5-list mailing list
rhelv5-list@(protected)
https://www.redhat.com/mailman/listinfo/rhelv5-list