On Sun, Jan 26, 2020 at 3:54 PM cagsm <cumandgets0mem00f@gmail.com> wrote:
.... waiting for completion to then continue with removing the leftover first small hdd and be done with physical stuff, then still needing to regrow the md127 device to larger capacity of the newer larger hdd disks used for it, and later regrowing the filesystem as well to make use of the additonal space as well.
I did remove the leftover small old hdd, and pyhsically removed it from the temporary sata port in use.
mdadm --fail /dev/md127 /dev/sdd1 mdadm --remove /dev/md127 /dev/sdd1
then "grew" the raid1 device back to only two participating devices:
mdadm --grow --raid-devices=2 /dev/md127
then grew the outer raid device to maximum size of the two new participating devices with their partitions:
mdadm --grow /dev/md127 --size=max
apparently/unfortunately I didnt wait for this to complete and already issued the growing of the actual real userlevel filesystem as well, guess the performance of the operations now does not give optimal results, as the growing of the outer md127 is still ongoing as I later discovered with looking at mdstats
mdadm --grow /dev/md127 --size=max resize2fs /dev/md127
although the resize2fs command returned to shell within a few seconds. I then re-added the bitmap again as well:
mdadm --grow /dev/md127 --bitmap=internal
The removal of the physical old small hdd also freed up some linux sdX device name as well that I used to work with for some other usb connected device that is important to this setup. Thanks for all the helping in this threads. TY. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org