# Moving Data more than double the key-value size stored

**URL:** <https://forums.foundationdb.org/t/moving-data-more-than-double-the-key-value-size-stored/1006>\
**Category:** Using FoundationDB\
**Created:** [January 11, 2019, 2:25pm UTC](https://forums.foundationdb.org/t/moving-data-more-than-double-the-key-value-size-stored/1006 "2019-01-11T14:25:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wmd](https://avatars.discourse-cdn.com/v4/letter/w/fbc32d/32.png) [@wmd](https://forums.foundationdb.org/u/wmd)\
**Post date:** [January 11, 2019, 2:25pm UTC](https://forums.foundationdb.org/t/moving-data-more-than-double-the-key-value-size-stored/1006/1 "2019-01-11T14:25:18Z")

</div>

We recently upgraded to FDB5.2 from FDB3 on several clusters. Only one exhibited this behavior. FDB was restarted after the new binaries and libraries were dropped in place and after some amount of time began healing except with more than double the amount of data stored:

`Moving data - 32404.500 GB`  
`Sum of key-value sizes - 8.361 TB`  
`Disk space used - 23.588 TB`

I would like to know how is 32404.500 calculated? In fact it was originally around 40T when healing began. There are 4 nodes running in `double` redundancy mode using the `ssd-1` storage engine with `32` processes spread across them.

Is this related to the bug:  
`Sometimes data distribution calculated the size of a shard incorrectly. [6.0.15] https://github.com/apple/foundationdb/pull/892` by any chance?

Any help much appreciated.