Description of problem: When using storage that is configured with a 4M block size, cloning fails with the following error: data-processor.go:328] exit status 1, blockdev: ioctl error on BLKGETSIZE64: Inappropriate ioctl for device Version-Release number of selected component (if applicable): 2.5.5 How reproducible: Unsure Steps to Reproduce: 1. Create source DV on storage with 4M block size 2. Create DV to clone source DV on storage with 4M block size Actual results: Cloning fails with above error message Expected results: Cloning should succeed Additional info: We should consider detecting larger block sizes and adapting our cloning block size automatically.
This GH issues [0] seems related. It appears calling blockdev on a non /dev path returns the above mentioned error. And we were in fact mounting our block devices on a non /dev path. However [1] fixed this for 2.5.x. So I am going to put this on QA [0] https://github.com/kubernetes-sigs/azuredisk-csi-driver/issues/714 [1] https://github.com/kubevirt/containerized-data-importer/pull/2031
Actually that PR was not merged, so it not fixed.
Seems like there is nothing left to do with this bug. The related CDI PR (https://github.com/kubevirt/containerized-data-importer/pull/2031) was closed.