zQUEz wrote:
I have similar issues to you, but I can tell you that it is an informational message, not a critical issue. Basically, the literature says a tunesys *should* fix this, and I even had 1 HP 2nd level tech tell me as much. When I pointed out that I have already done a tunesys I got another tech respond that it won't fix it and I need to retune all the VV's associated with the LD's. What they don't point out is that because I have all my VV's wide striped across all LD's (whole point of 3PAR right?), that to do that would mean I would run out of tier1 (FC) long before I got my VV's retuned.
*beating head against wall*
I am on 3.1.2MU3 but the inconsistencies were from 3.1.1MU3. I "suspect" what happened in our case is someone changed the CPG settings, and then changed it back but in the intrim some VV data got written to the old settings.
My understanding of the technogy is different.
Your data is wide striped across all physical disks. From the physical disks, 3par creates chunklets. 3par then uses chunklets to build logical disks according to the raid and availability specifications in your cpg.
Thus, your data is wide striped across all pd's, not ld's.
So what you would want to do is identify which vvs are using those ld's and tune them.