Sparsely allocated files are expanded to full size when using mover (cache -> array). (6.5.2-rc2)

I am running into an issue where a sparse file is created in cache share by docker. The file is then moved from cache share to the array using mover. On this a full size file is written to the array rather then only the data used.

There is nothing extraordinary in the logs. Just says that the particular file is being moved and the array drive starts writing to itself until the sparse file is fully expanded.

I am on 6.5.2-rc2