HPE Storage Users Group

I have a 3PAR 7400 and I added two disk enclosure with 24 drives to it.
The licensing is is as follows:
System is licensed for unlimited disks.

License features currently enabled:
3PAR OS Suite
Adaptive Flash Cache
Adaptive Optimization
Autonomic Rebalance
Dynamic Optimization
Management Plug-In for VMware vCenter
Peer Motion
Peer Persistence
Priority Optimization
Recovery Manager for Oracle
Recovery Manager for VMware vSphere
Remote Copy
System Reporter
Thin Conversion
Thin Copy Reclamation
Thin Deduplication
Thin Persistence
Thin Provisioning (10240000G)
Virtual Copy
VSS Provider for Microsoft Windows

Also I ran the admithw and tunesys already

So for my question
I see the new disk added but it appears that it didn't re-balance across the disks like I was thinking it would.
I read that the data will not evenly distributed to the new disks, until you use dynamic optimizer to rebalance.
Is this automatic or do I need to do something?

cage 20 and 21??

if my memory serves me right, 20 cages is max for 7400 and you’ve probably exceeded the supported number of cages.

what does «showpd -state» say in CLI?

And what did admithw say?


Generally admithw should add the hardware and tunesys should balance… The tunesys task may shed some light if pd state and admithw looks okay.

Thanks for the reply @MammaGutt

Just a quick update. On one of my 3PAR Systems I am seeing it spread the data across the new disks.

The other 3PAR System I am seeing the following log entry

2023-06-02 15:06:06 EDT Updated Unable to perform dry run analysis when servicemag is active.
2023-06-02 15:06:06 EDT Updated *********************************************************
2023-06-02 15:06:06 EDT Updated * Tunesys task (id 17766) has terminated
2023-06-02 15:06:06 EDT Updated * Reason: expected integer but got ""
2023-06-02 15:06:06 EDT Updated *********************************************************
2023-06-02 15:06:06 EDT Completed scheduled task.

I think this may be my problem but I'm not too sure how to remediate it.

Froda wrote:Thanks for the reply @MammaGutt

Just a quick update. On one of my 3PAR Systems I am seeing it spread the data across the new disks.

The other 3PAR System I am seeing the following log entry

2023-06-02 15:06:06 EDT Updated Unable to perform dry run analysis when servicemag is active.
2023-06-02 15:06:06 EDT Updated *********************************************************
2023-06-02 15:06:06 EDT Updated * Tunesys task (id 17766) has terminated
2023-06-02 15:06:06 EDT Updated * Reason: expected integer but got ""
2023-06-02 15:06:06 EDT Updated *********************************************************
2023-06-02 15:06:06 EDT Completed scheduled task.

I think this may be my problem but I'm not too sure how to remediate it.

start with admithw and checkhealth -svc -detail

that should give some starting points.
maybe also showtask -d 17766

Ok here is what I've found,

After running the (checkhealth) I see the following message
PD Magazines that are being serviced 32

I scroll down a little bit and see

cage 20 and cage 21 are : Magazine is being serviced

These are the two cages that I added

(showpd) all looks normal (normal state)

I think this is where the issue stems from is the new cages are stuck in a being serviced status

Checked (showtask -all) and there are some system tasks that are running
(move_back_chunklet), (remove_expired_vvs), (check_slow_disk)

this might be something
Also saw this message
PD Unbalanced PD types in Cages 12 -> Cages 3, 4, 5, 6, 15, 17 for both paths

my guess is that they are in a servicing state as you’ve added more cages than the system supports and the only reason for that would be cage replacement which would be a service action.