Alain, the default value is always the recommmended value. variance of 1% is the default and recommended value but in your case the variance was too high. During rebalancing if a tdat is busy handling active IO, vmax skips that tdat and moves on to the other tdat, this causes a slight variance. I believe you must check the audit logs to find out if the tdats were added to the pool?  regards, Saurabh
I have VMAXs in production with thin provisionning for a few month now, and I note a stange behaviour. In most of our thin pools, the TDAT's does not appear to be all filled at the same level. The skew can go from one TDAT full at 56%, to another TDAT in the same pool at 96%. I wonder how this could happen, as nothing has been changed in the pools constitution, no TDAT were added or removed, only TDEVs were bound or removed from the pools.  A corrective action is probably do initiate a balancing of the pools, but my questions: Is there a parameter that would automatically keep the TDAT well balanced? Is it a recommendable preventive action to start balancing of the pools on a regular basis?   Any suggestion is welcome.
Thin Pools, why do they need to be rebalanced after a while?