Bug Fixes

BZ#783162

Prior to this update, in some cases, Initial Program Load (IPL) did not work after calling the zipl boot loader. Consequently, incorrect bootmap could be used during initialization and an incorrect kernel could be loaded. This update adds the fsync() function, which ensures that all correct and necessary data is written to disk.

BZ#787685

Previously, the qethconf tool for configuring network interfaces worked in the case-sensitive manner. Consequently, qethconf was searching for non-existent match of IPv6 addresses when these were written in capital letters. With this update, qethconf handles IPv6 addresses as expected and IPv6 searches are now case-insensitive.

BZ#809462

Due to an incomplete monitor record header for the stop record, unused monitor records of stopped processes were not halted correctly and continued to show up in the z/VM hypervisor monitor stream. The header data has been completed, thus preventing the stoppage of unused records.

BZ#820262

Prior to this update, the buffer used for writing error messages was too small. As a consequence, when trying to write changes to a read-only device using the fdasd program, the buffer overflew. This update adds fprintf() function, which writes directly to the stderr stream without the buffer. As a result, buffer overflows no longer occur.

BZ#820263

Previously, the lsdasd(8) manual page did not contain the -b option. In adddition, the lsdasd command returned "1" instead of "0" output, when the -h option was specified. The missing -b option has been added to the manual page and the outputs for the -h option have been correctly specified, thus fixing the bug.

BZ#857816

When the zipl boot loader was run on the Direct Access Storage Device with the Fixed Block Access format (FBA DASD), previously initialized Physical Volume (PV) on the partition could no longer be recognized by LVM. With this update, the cache for the disk and partition block devices is flushed before installing the IPL record, thus fixing the bug.

BZ#837305

Previously, a Small Computer System Interface (SCSI) device was not available immediately after registration. As a consequence, the lsluns script failed to recognize the LUN0 and WLUN attachment with the following error message:

Cannot attach WLUN / LUN0 for scanning

To fix this bug, multiple checks for SCSI registration with the LUN0 and WLUN attached via the unit_add option have been added and SCSI mid layer now successfully completes the SCSI device registration.

BZ#906837

The ziorep_config configuration report is supposed to ignore SCSI disks that are not part of the multipath device mapper when creating the multipath mapper report. Previously , ziorep_config failed to correctly ignore SCSI disks which caused get_line() function to return n/a output if a sysfs attribute did not exist. This output is stored in the mp_dev_mm hash key so its value could not be used in a check for being undefined. With this update, the mp_dev hash field remains undefined, if no multipath device is found, thus fixing the bug.

BZ#828128

Previously, the lsluns script checked for sg kernel subsystem functionality before scanning available LUNs or showing attached LUNs. Consequently, lsluns failed to list available LUNs and to show attached LUNs with the -a option. Early kernel subsystem availability check has been removed to fix this bug.

BZ#851096

Previously, the /etc/profile.d/s390.sh script contained incorrect equation syntax. As a consequence, when the zsh shell on s390x architecture was started, the following error message appeared:

/etc/profile.d/s390.sh:4: = not found

The script has been fixed and no error messages are now returned.