Description of problem:

• Customer is trying to DVM migrate a large volume (>3 TB) from 3.11 cluster to 4.13

Version-Release number of selected component (if applicable):

• MTC 1.7.14
• Migration of application between 3.11 and 4.13
• ODF

How reproducible:

• All the time on customer environment

Steps to Reproduce:
1. Have an application with a large volume and lots of files
2. Run a stage migration. In this case it ended with warnings on the DVM / rsync side
3. Run cutover migration. It fails to start rsync-server POD in destination host with: 'timed out waiting for the condition' while trying to mount the volume

Actual results:

• Cutover migration cannot start. 

Expected results:

• volume migration should succeed

Additional info:

• In the kubelet logs there seem to be indication that chown/chmod could be the culprit here

Setting volume ownership for /var/lib/kubelet/pods/8905d88e-6531-4d65-9c2a-eff11dc7eb29/volumes/kubernetes.io~csi/pvc-287d1988-3fd9-4517-a0c7-22539acd31e6/mount and fsGroup set. If the volume has a lot of files then setting volume ownership could be slow, see https://github.com/kubernetes/kubernetes/issues/69699