RHBA-2007:0991 - Bug Fix Advisory

Topic

Updated cmirror-kernel packages that fix module loading issues and various
bugs are now available for Red Hat Enterprise Linux 4.6, kernel release
(2.6.9-67.EL).

Description

The cmirror-kernel packages provide support within the kernel for cluster
mirroring.

These updated packages fix the following bugs:

• a bug was fixed which caused the cmirror write path to appear deadlocked

after a successful recovery.

• a bug was fixed which caused a cluster mirror to be out of sync when

nominal I/O overlapped recovery I/O. This may have caused a cluster mirror
to hang.

• a deadlock caused by a flush/recovery collision after a mirror leg and

node failure was fixed. A "dm-cmirror: Flush/recovery collision" error was
logged.

• a clvm deadlock caused by a suspended mirror resulted in cmirror server

elections failing with a "dm-cmirror: Failed to receive election results"
error. This has been resolved in these updated packages.

As well, these updated cmirror-kernel packages are in sync with the latest
kernel (2.6.9-67.EL). The modules in earlier cmirror-kernel packages failed
to load because they did not match the running kernel. It was possible to
force load the modules; however, with this update, users no longer need to.

Users are advised to upgrade to these latest cmirror-kernel packages, which
are updated for use with the 2.6.9-67.EL kernel.

Solution

Before applying this update, make sure that all previously-released
errata relevant to your system have been applied.

This update is available via Red Hat Network. Details on how to use
the Red Hat Network to apply this update are available at
http://kbase.redhat.com/faq/FAQ_58_10188

Affected Products

• Red Hat Enterprise Linux Resilient Storage for x86_64 4 x86_64
• Red Hat Enterprise Linux Resilient Storage for x86_64 4 ppc
• Red Hat Enterprise Linux Resilient Storage for x86_64 4 ia64
• Red Hat Enterprise Linux Resilient Storage for x86_64 4 i386

Fixes

• BZ - 239856 - failed server election due to suspended mirror log causes clvm deadlock
• BZ - 257881 - Flush/recovery collision leads to deadlock after leg and node failure
• BZ - 290821 - cmirror write path appears deadlocked after recovery is successful
• BZ - 291521 - Cluster mirror can become out-of-sync if nominal I/O overlaps recovery I/O

CVEs

(none)

References

(none)