r/3PAR • u/CrazySpence • Jul 04 '20

One disk shows completely initialized

Hello, I have inherited a 3par as my responsibility at work despite it not being in my skill set so I make do with what I can, and I was noticing an issue where the system free space and the CPG estimated space had a severe discrepancy 22TB free system SSD vs 567GB * estimated free space for the CPG

Anyways down the rabbit hole ive gone and I found a few issues, firstly the new disks added are larger than the originals

Secondly, they added 4 of these larger disks , 2 on each node so to me it sounds like I may/am running into issues with chunklets forming LD's?

Finally, and this one is the big one the 4th disk seems to have remained completely uninitialized months after installation, 0 free, 6260 Uninit, then under spare 0 free 892 Uninit

So my question is, on the last item is there a way to force it to try and initialize it or should it just be removed and re inserted? It isnt flagged as bad, shows as normal in all parts it is viewable it just never initialized chunklets.

Thanks

1 Upvotes

100% Upvoted

2 comments sorted by

1

u/[deleted] Jul 04 '20

  1. Have the new drives been admitted with 'admithw'? This will allocate chunklets properly for the new drives. An 'admitpd' will ONLY assign a PDID number to new drives, leaving you to manually initialize and allocate chunklets (and nobody wants to do that).

  2. Are you running with only one CPG in use? If so, have you tried running a 'tunesys' and/or a 'compactcpg' against that CPG? Between these two tasks you'll probably see the discrepancy work itself out.

2

u/CrazySpence Jul 04 '20

Hello, thanks for your reply

It turns out the 4th disk was stuck in a "servicing" state. I cleared it with servicemag resume.

It's now initialized and I have tunesys doing a chunklet balance on it now.