+++ This bug was initially created as a clone of Bug #903212 +++
Description of problem:
During expanding the size of RAID1 or RAID5 volume the resync process is reported in /proc/mdstat but there is no information about it in the volume’s metadata. Therefore if the RAID volume was stopped during the process of size expansion all information about this progress would be lost, because no checkpoint is saved in the metadata.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create RAID1 or RAID5 volume of size less than maximum and wait for its normal state, e.g.:
# mdadm -C /dev/md/imsm -amd -e imsm -n 3 /dev/sda /dev/sdb /dev/sdc
# mdadm -C /dev/md/volume -l5 --size 10G -n 3 /dev/sda /dev/sdb /dev/sdc
2. Expand the size of a RAID volume providing new size, e.g.:
# mdadm -G /dev/md/volume --size max
3. Check metadata during rebuild process:
# mdadm -E /dev/md/imsm
Metadata contains no information about the resync process ongoing during expanding the size of RAID1 or RAID5 volume. No checkpoint is saved. Metadata shows normal state of the volume.
Metadata contains information about the resync process ongoing during expanding the size of RAID1 or RAID5 volume. Checkpoint is saved.
Patch for this bug has been sent to linux-raid:
[PATCH] Add updating component_size to manager thread of mdmon
included as git commit 4edb8530e889fc7b5e1b5471a0fbfd6c3c116b4a in upstream
mdadm-3.2.6-18.fc19 has been submitted as an update for Fedora 19.
mdadm-3.2.6-18.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mdadm-3.2.6-18.fc19'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
mdadm-3.2.6-19.fc19 has been submitted as an update for Fedora 19.
mdadm-3.2.6-19.fc18 has been submitted as an update for Fedora 18.
mdadm-3.2.6-19.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
mdadm-3.2.6-19.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.