We've seen rare cases with workloads that use sparse files that will expand beyond the capacity of a target pvc's size due to rysnc transferring the empty space of a sparse file. We think this should be handled with a `–sparse` flag passed through to rsync, but ideally we'll want to warn about the case ahead of time.

It would be good to begin to test this case in our own environments as part of QE's process, this task represents our desire to test this, although it's quite an edge case and therefore fairly low priority.

See relates to issue for the eng story.