Correct, but keep in mind I was asking for dedupe rate not allocation. Your description is exactly what it would be nice to see per LUN. Volume A has 3 logical blocks and 1 is shared meaning it has a 33% reduction rate
I understand it is an interesting problem tracking that per volume, but certainly something that could be done or could be run via a utility after the fact perhaps.
As for the other utility that is useful for sizing, but not really for looking into sizing after the fact or for new data. Really would be nice to have a way to do it on the XtremIO not the host side for trouble-shooting purposes.