I have a 8.1.2 7-mode box that I added 23 SAS drives to a new raidgroup in an aggregate. Even though I specified 23@450g for the disk add, it brought four 600GB SAS dirives into the raidgroup, which used all of my 600GB spares. The 600GB drives are the parity, dparity and two data disks in the new raidgroup. I need to replace these with the correct 450GB size drives, which the remaining 19 drives in the rg are. When trying a disk replace I receive a " Disk 6c.20.21 is not of appropriate size" message. I've tried the disk replace with and without the -m flag. I'm reluctant to try the -f flag unless someone can verify that this will work, or not.
I also tried a disk fail and received -
WARNING! There is no spare disk available to which to copy. Are you sure you want to continue with disk fail (y/n)?
Any suggestions? I can't do a vol move to relocate the vols to other aggrs as they are CIFS with active shares and we can't take an outage.
Unfortunately, to my best knowledge this is impossible (using officially known tools at least). Parity and dparity disks consume full disk size when allocated initially, so you cannot replace them with smaller disks. They could be some undocumented internal means to do it 🙂
As per this spare disk list, you have sufficient spare disks of SAS 600GB 15krpm.
Reviewing your RAID configuration I found that 'Used Size' of 600GB disks are not downsized. Usually, 'Used Size' of larger disks are downsized to that of smaller disks when adding larger disks into RAID group of smaller disks.
As previously mentioned, adding larger disk as parity brings this odd state. This behavior is described in below.