8.114. mdadm

Bug Fixes

BZ#903212

Previously, during expanding the size of an Intel Matrix Storage Manager (IMSM) RAID1 or RAID5 volume, the resynchronization process was reported in the /proc/mdstat file but there was no information about the process stored in the volume's metadata. Consequently, if the RAID volume was stopped during the process of size expansion, all information about this progress was lost and the resynchronization would be restarted from the beginning on the next array reassembly. A patch has been been applied to address this problem, and information is now stored in metadata as expected in the described scenario.

BZ#950545

Prior to this update, the mdadm utility did not work correctly when attempting to write a superblock onto a defective drive. Consequently, mdadm could terminate unexpectedly with a segmentation fault if it encountered a write error. This bug has been fixed and mdadm no longer crashes in this scenario.

BZ#955972

Previously, the mdadm utility did not work correctly if a rebuild of an Intel Matrix Storage Manager (IMSM) RAID5 volume was started in Option ROM (OROM). Consequently, the RAID5 volume was in the "degraded" state once booted into the operating system and the rebuild did not proceed. A patch has been applied to address this problem and rebuilding IMSM RAID5 volumes now completes successfully in the described scenario.

BZ#956016

Previously, when an Intel Matrix Storage Manager (IMSM) volume was being reshaped, the "mdadm -Ss" command used for stopping the process did not work properly. Consequently, on the first run of "mdadm -Ss", only the volume was stopped but the container was left in place, and a second execution of the command was necessary. This bug has been fixed and the command now works as expected during a volume's reshape.

BZ#995105

Previously, when an Intel Matrix Storage Manager (IMSM) RAID10 volume was being resynchronized or rebuilt, stopping the process after 50% completion did not work properly. As a consequence, the processes did not proceed correctly after reassembling, and the data became corrupted. With this update, resynchronization and rebuild work correctly in this scenario.

BZ#1001627

Prior to this update, when an Intel Matrix Storage Manager (IMSM) RAID1 or RAID10 volume was being rebuilt and this process was stopped, an attempt to resume the rebuild was not successful. Consequently, the rebuild did not start even when a new drive was added to the container, and metadata contained incorrect information. This bug has been fixed and resuming a rebuild now works properly in the described scenario.

BZ#1010859

Previously, the mdadm utility did not work correctly when a disk failed in an Intel Matrix Storage Manager (IMSM) RAID volume. Consequently, the failed disk was removed neither from the volume nor from the container, the volume was not in the "degraded" state, and the rebuild could not start. With this update, mdadm handles failed disks in RAID volumes properly.