Hello,
you see the disks trough the module B and module A.
If you issue the command >storage show disk <disk-id>
example: >storage show disk 0b.19
You should see two paths for it?
So it's "random" which pat will be used as primary, and you see it in sysconfig -r / aggr status -r command output.
You have mixed rpms in the same raidgroup.
supported, not optimal.
You just have to know, that 15k disks connot work in that speed, because there is also 10k disks in the same rg.
Rg rpm would be 10k.
If you have different size of disks in the same rg, then the usable size of the disk will be mainly the smallest one.
Example: parity disks are 72GB:
You add 2TB disk to this aggregate, you'll lose 1,9xTB, from that disk. (parity needs to be calculated to smaller disks).
You can succesfully add bigger disks to rg, if the parity disks are large enough to hold the parity.
You cannot replace 72GB disk with 2TB disk. Replace command issued, it will copy the data from 72GB disk to 2TB disk and it will work as 72GB.
Disk fails, and only available spare is 2TB for this broken 72G disk. ONTAP will reconstruct the disk from the paritys, and usable size will be 72GB.
Br.
Ismo.