Created attachment 957867 [details] output from mdstat, mdadm, partitions, kernel etc Description of problem: When using mdadm to grow or shrink a RAID1 array to a fixed size beyond 2TB the request is ignored. If 'max' is used then the full 3TB size is correctly set. Version-Release number of selected component (if applicable): mdadm-3.3-7.fc20.x86_64 kernel-3.17.2-200.fc20.x86_64 How reproducible: every time for any size > 2TB Steps to Reproduce: 1. RAID1 with 2 x 3TB disks, each with single partition (sdb1, sdc1) 2. Setting size to 'max' results in a 3TB array 3. Trying to set any size between 2 & 3TB is ignored 4. Setting sizes < 2TB works Actual results: [root@shark ~]# mdadm /dev/md0 --grow --size=max mdadm: component size of /dev/md0 has been set to 2930134016K [root@shark ~]# cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdc1[3] sdb1[2] 2930134016 blocks super 1.2 [2/2] [UU] [root@shark ~]# mdadm /dev/md0 --grow --size=2900000000 mdadm: component size of /dev/md0 unchanged at 2930134016K [root@shark ~]# mdadm /dev/md0 --grow --size=2147483647 mdadm: component size of /dev/md0 has been set to 2147483647K [root@shark ~]# mdadm /dev/md0 --grow --size=2900000000 mdadm: component size of /dev/md0 unchanged at 2147483647K Expected results: Setting any size value less than the 'max' should work. Using a size slightly less than the max is useful in case a future drive replacement is slightly smaller (as recommended in man page). Additional info: Using strace suggests that mdadm is probably not at fault, more likely this is a kernel md issue. mdadm seems to write the correct values into the /sys files but the kernel ignores them, e.g. setting 2.9TB: open("/sys/block/md0/md/dev-sdc1/size", O_WRONLY) = 4 write(4, "2900000000", 10) = 10 ... open("/sys/block/md0/md/component_size", O_RDONLY) = 4 read(4, "2147483647\n", 50) = 11 When the array was first created several years ago it contained 2 x 1.5 TB disks. These were replaced with the current 3TB disks. A selection of data from /proc/mdstat, mdadm --examine, /proc/partitions, kernel etc. are attached.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.