Page 1 of 1

[7200c] - Issues with TDVV "overallocated"

Posted: Fri Dec 15, 2017 9:14 am
by Cykani
Hello Guys,

This is my problem :

Code: Select all

Id Name             Prov Type  Rsvd  Used Rsvd Used Used Wrn Lim     Rsvd     Used  Used Wrn Lim Tot_Rsvd    VSize   Compaction    Dedup
 1 .srdata          full base     0     0    0    0  0.0  --  --    61440    61440 100.0  --  --    61440    61440           --       --
 0 admin            full base     0     0    0    0  0.0  --  --    10240    10240 100.0  --  --    10240    10240           --       --
34 CSV              tdvv base   256     2    0    0  0.0  --  --     1027        3   0.1   0   0     1283     5120       1004.3     10.0
25 dboracle1        tdvv base 17266 16924    0    0  0.0  --  --  1452905  1446806 353.2  80   0  1470171   409600          1.0      1.0
30 dboracle2        tdvv base 17166 16730    0    0  0.0  --  --  1413143  1410202 344.3  80   0  1430309   409600          1.0      1.2
36 quorum_hyp_bdic1 tdvv base   256     3    0    0  0.0  --  --     1079       56   1.1   0   0     1335     5120         87.9      1.0
39 Vol1_DQ_BDAC1    tpvv base   640   323    0    0  0.0  --  --    16512       93   0.0  80   0    17152   614400       1476.9       --
48 Vol1_DQ_BDIC1    tpvv base   512   282    0    0  0.0  --  --    66944    50612   8.2  80   0    67456   614400         12.1       --
43 Vol1_DQ_BDKC1    tpvv base  1152   885    0    0  0.0  --  --  1146496  1142348  48.5  80   0  1147648  2355200          2.1       --
40 Vol1_DQ_CKC1     tpvv base  1536  1216    0    0  0.0  --  --  1604096  1587732  64.6  80   0  1605632  2457600          1.5       --
41 Vol1_DQ_KKC1     tpvv base   512   214    0    0  0.0  --  --    31488    15191   2.5  80   0    32000   614400         39.9       --
42 Vol1_INF_BDIC1   tpvv base   640   382    0    0  0.0  --  --   481536   465488  56.8  80   0   482176   819200          1.8       --
38 Vol1_PRD_BDIC1   tdvv base 12221 11915    0    0  0.0  --  --  2183415  2166942 111.7  80   0  2195636  1939968          1.0      1.5
37 Vol1_PRD_BDKC1   tdvv base 22124 21732    0    0  0.0  --  --  4053015  4031741 123.0  80   0  4075139  3276800          1.0      1.3
47 Vol1_PRD_CKC1    tdvv base  2256  1944    0    0  0.0  --  --   297118   293376  28.0  80   0   299373  1048576          3.6      6.3
45 Vol1_PRD_KKC1    tdvv base   833   554    0    0  0.0  --  --    66903    64399   5.7  80   0    67736  1126400         17.3     17.7
50 Vol1_PRD_RZBC1   tdvv base   966   711    0    0  0.0  --  --    92611    89690  10.9  80   0    93577   819200          9.1     11.2


Most of my tdvv volumes are "overallocated". I just want to know how couldi fix it as i don't have DO license.

Thanks in advance

Re: [7200c] - Issues with TDVV "overallocated"

Posted: Fri Dec 15, 2017 10:37 am
by JohnMH
It could be a couple of things, either something changed at the host file system layer, or possibly free space in the DDS being slow to reclaim due to the firmware level and older hardware.

These appear to the be the offending volumes and are all dedupe volumes:

Vol1_PRD_BDKC1
dboracle1
dboracle2
Vol1_PRD_BDIC1

However since both reserved and used space are pretty close it could be that some large changes have occurred at the file layer and the array hasn't been made aware of these. First thing I'd try would be to run an unmap to signal the reserved space can be reclaimed.

Have a look at this WP appendix A for reclaim techniques : https://h20195.www2.hpe.com/V2/Getdocument.aspx?docname=a00006358enw

Re: [7200c] - Issues with TDVV "overallocated"

Posted: Fri Dec 15, 2017 2:10 pm
by Cykani
And what about reducing the sparing volumes ?

Re: [7200c] - Issues with TDVV "overallocated"

Posted: Tue Dec 19, 2017 2:58 am
by RitonLaBevue
Maybe you could benefit of an Inform OS update to jump to 3.3.1 : some major issues with TDVV v2 are fixed, relating to space reclaim...

Re: [7200c] - Issues with TDVV "overallocated"

Posted: Tue Dec 19, 2017 1:32 pm
by JohnMH
Yes you could reduce the sparing level but it would potentially reduce availability and wouldn't really solve the problem at hand, only mask it temporarily. Try the unmap initially and make sure you're on a current firmware release.