1.40. dmraid

Updated dmraid packages that fix several bugs are now available.

The dmraid packages contain the ATARAID/DDF1 activation tool. The tool supports RAID device discovery and RAID set activation, and displays properties for ATARAID/DDF1-formatted RAID sets on Linux kernels using the device-mapper utility.

These updated dmraid packages fix the following bugs:

* the dmraid-events package was installing the dmevent_syslogpattern.txt file to the /etc/logwatch/scripts/services directory. The dmevent_syslogpattern.txt file is used by the logwatch service to record event logs. SELinux does not allow write access to the /etc/logwatch/scripts/services directory, and as a result the logwatch service was prevented from updating the log file. The dmraid-events package has now been updated to install the log file at /var/cache/logwatch/dmeventd/syslogpattern.txt, and the log file is updated as expected. (BZ#513402)

* after a hard disk drive rebuild has been completed using dmraid, the LED lights on each disk belonging to the rebuilt RAID volume should turn off. Previously, if the rebuild was initiated manually using the 'dmraid -R' command, the light on the spare disk would remain illuminated, incorrectly indicating that the disk was still being built. When rebuilding automatically with the libdmraid-events library, the light would not remain lit as expected. The dmraid packages have been updated to turn off the light correctly after a manual disk rebuild, and the drive light now correctly indicates the drive state. (BZ#514497)

* dmraid binaries in the /sbin directory previously relied on libraries in the /usr directory. Since the /sbin directory typically only contains programs executed by the root user, reliance on libraries in the /usr directory could result in reference conflicts. The dmraid packages have been updated to no longer rely on the /usr directory, and library references are now improved. (BZ#516852)

* the dmraid-events-logwatch tool would take ownership of directories that were already owned by the logwatch package. This included the following directories:

* /etc/logwatch/conf * /etc/logwatch/conf/services * /etc/logwatch/scripts * /etc/logwatch/scripts/services

As a consequence, the dmraid-events-logwatch tool and the logwatch package would conflict. The dmraid-events-logwatch package has been updated to own only /etc/logwatch/scripts/services/dmeventd directory, and the conflict no longer arises with the logwatch package. (BZ#545876)

* modifications to Intel support in the libdmraid tool caused the SONAME field to change. This caused compatibility issues in python-pyblock symbolic links. The version number in the libdmraid tool's file name has been updated, which caused the dependencies to be automatically re- generated during the build process. The symbolic link is now repaired and there are no compatibility issues between libdmraid and python-pyblock. (BZ#556254)

* the pthread_mutex_trylock symbol was not being exported against the libpthread tool. As a consequence, the libdmraid-events-isw.so object would not be loaded during activation of a RAID5 volume library, reporting that pthread_mutex_trylock was an undefined symbol. Linking has now been added to the libpthread tool, and pthread_mutex_trylock is successfully referenced in the libdmraid-events-isw.so object. (BZ#567922)

All dmraid users should upgrade to these updated packages, which resolve these issues.