Este conteúdo não está disponível no idioma selecionado.
1.10. cmirror
1.10.1. RHBA-2011:0057: bug fix update
An updated cmirror package that fixes various bugs is now available for Red Hat Enterprise Linux 5.
The cmirror package is necessary for LVM-based mirroring (RAID1) in a cluster environment.
This update fixes the following bugs:
* A data corruption may have occurred when using 3 or more mirrors. With this update, the underlying cluster code has been modified to address this issue, and the data corruption no longer occurs. ( BZ#456575, BZ#471291)
* Prior to this update, cmirror did not work properly in a cluster that was composed of systems with different versions of Red Hat Enterprise Linux 5. This has been fixed, and running cmirror in such environment now works as expected. ( BZ#533204)
* In a two device allocation, the failure of both the primary and the log device may have caused the sync attempt to fail and mirrors to stop responding to I/O requests. With this update, this error no longer occurs, and such mirrors now respond as expected. ( BZ#561984)
* Due to the inclusion of the linux/kdev_t.h header file, the use of "MAJOR" or "MINOR" macros in the source code may have caused a device number to be associated with a wrong device. With this update, this error no longer occurs, and device numbers are now always associated with correct devices. ( BZ#631925)
All cmirror users are advised to upgrade to this updated package, which resolves these issues.
1.10.2. RHBA-2010:0883: bug fix update
An updated cmirror package that fixes a bug is now available.
The cmirror package is necessary for LVM-based mirroring (RAID1) in a cluster environment.
This updated cmirror package fixes the following bug:
* Previously, the MAJOR/MINOR macros caused a device number miscalculation, which could result in an association of a given device number with the wrong device. With this update, the miscalculation no longer occurs and the given device number is associated with the right device. ( BZ#640912)
All users of cmirror are advised to upgrade to this updated package, which resolves this issue.