Skip to content

"SLC6X: system environment/base: mdadm

mdadm - The mdadm program controls Linux md devices (software RAID arrays)

Website: http://www.kernel.org/pub/linux/utils/raid/mdadm/
License: GPLv2+
Vendor: Scientific Linux CERN, http://cern.ch/linux
Description:
The mdadm program is used to create, manage, and monitor Linux MD (software
RAID) devices.  As such, it provides similar functionality to the raidtools
package.  However, mdadm is a single program, and it can perform
almost all functions without a configuration file, though a configuration
file can be used to help with some common tasks.

Packages

mdadm-3.3.4-8.el6.i686 [360 KiB] Changelog by Xiao Ni (2017-01-26):
- Cannot assemble IMSM array with domain policy in mdadm.conf and
  RAID level migration in container with 2 arrays breaks both arrays 
- Resolves bz1413937 and bz1413615
mdadm-3.3.4-1.el6_8.5.i686 [360 KiB] Changelog by Jes Sorensen (2016-06-21):
- Fix problem with reshaping IMSM arrays, where a new reshape could be
  launched before the first reshape had fully completed, leading to
  unpected results.
- Resolves bz1348544
mdadm-3.3.4-1.el6.i686 [358 KiB] Changelog by Xiao Ni (2015-12-09):
- Update to mdadm-3.3.4
- Resolves bz1248989
mdadm-3.3.2-5.el6.i686 [353 KiB] Changelog by Jes Sorensen (2015-05-19):
- Fix race condition when assembling IMSM volumes with mdadm -As
- Resolves bz1146994
mdadm-3.3-6.el6_6.1.i686 [349 KiB] Changelog by Jes Sorensen (2014-11-12):
- Fix problem with mdadm.conf AUTO=-all not being handled correctly
- Resolves bz1162976
mdadm-3.3-6.el6.i686 [349 KiB] Changelog by Jes Sorensen (2014-09-03):
- Fix problem with reshape of IMSM RAID arrays failing to start
- Disallow IMSM arrays spanning multiple controllers
- Fix problem with reshape failing to restart when reassembling IMSM RAID
- Resolves bz1136880, bz1136891, bz1136903
mdadm-3.2.6-7.el6_5.2.i686 [344 KiB] Changelog by Jes Sorensen (2014-04-07):
- Gracefully exit if mdmon received SIGTERM to avoid data corruption
- Resolves bz1084676
mdadm-3.2.6-7.el6.i686 [344 KiB] Changelog by Jes Sorensen (2013-10-09):
- Check for DM_UDEV_DISABLE_OTHER_RULES_FLAG instead of
  DM_UDEV_DISABLE_DISK_RULES_FLAG in 65-md-incremental.rules 
- Resolves bz1015514
mdadm-3.2.5-4.el6_4.3.i686 [341 KiB] Changelog by Jes Sorensen (2013-10-04):
- Z-Stream fix
- Fix problem with mdadm segfaulting if trying to write superblock
  onto a defective drive resulting in a write error.
- Resolves bz1009243
mdadm-3.2.5-4.el6_4.2.i686 [341 KiB] Changelog by Jes Sorensen (2013-08-14):
- Z-Stream fix
- Fix problem with mdadm segfaulting if trying to write superblock
  onto a defective drive resulting in a write error.
- Resolves bz1001493
mdadm-3.2.5-4.el6_4.1.i686 [341 KiB] Changelog by Jes Sorensen (2013-05-07):
- Z-Stream fix
- Fix problem with IMSM metadata where resync progress would be lost
  if an array was stopped during ongoing expansion of a RAID1/5 volume.
- Fix problem with IMSM RAID5 not rebuilding after reboot
- Resolves bz958024, bz960612
mdadm-3.2.5-4.el6.i686 [340 KiB] Changelog by Jes Sorensen (2012-12-06):
- Fix typo in error message in fix for 880208. No code functional change
- Resolves bz880208
mdadm-3.2.3-9.el6.i686 [337 KiB] Changelog by Jes Sorensen (2012-04-26):
- Correctly fix failure when trying to add internal bitmap to 1.0 arrays
- Resolves bz811282
mdadm-3.2.2-9.el6.i686 [324 KiB] Changelog by Jes Sorensen (2011-11-04):
- Fix problem where an IMSM RAID is rejected because of unexpected
  attribute settings. Additional fix being extra cautious from -8.
- Resolves: bz733153
mdadm-3.2.2-1.el6_1.2.i686 [320 KiB] Changelog by Doug Ledford (2011-07-27):
- Minor fix for readding devices specifically related to writemostly usage
mdadm-3.2.1-1.el6.i686 [311 KiB] Changelog by Doug Ledford (2011-03-28):
- Update to latest upstream release
- Don't report mismatch counts on either raid1 or raid10 devices
- Check both active and idle arrays during raid check runs
- Move raid-check script to /usr/sbin, add a crontab entry to /etc/cron.d
  and mark it config(noreplace) so that users can select their own
  raid check frequency and it will be preserved across updates
- Allow the raid check script to set both the cpu and io priority on the
  raid check process in an effort to minimize the impact to users on the
  system
- Related: bz633306

Listing created by repoview