Changed array composition, mdadm --detail still shows the old array size
- by Prody
I have a machine with 8 disks.
I installed it with my hoster's install automation (it's OVH, I don't have physical access to it).
The machine installed correctly, but it made an array that I wanted to change.
It created a raid5 array across 5/8 disks and I've changed it to raid10 across 8 disks.
I've done this by first --stopping the old array and then --creating the new array.
It warned me that a previous array was there, but I chose to continue.
So it created the array, spent 10ish hours syncing it and now that it's ready I get this strange behavior:
When I fdisk p on it, I see the correct size. But when I mdadm --detail it I see the old array's size even tho I get the new composition and level.
When I try to pvcreate on it, i get the old size again for some reason.
Did I have to do something else? Did I miss something?
