Large VDO device not started after reboot

Issue

• The system has a large vdo device of 180 TB logical size and 60 TB physical size. During each reboot, the system fails to mount this vdo device. However after ~20-25 minutes post reboot, users could mount it manually. There are following errors observed while booting up the system:

  kernel: uds: loading out-of-tree module taints kernel.
  kernel: uds: modprobe: loaded version 8.0.6.2
  kernel: kvdo: modprobe: loaded version 6.2.8.7
  kernel: kvdo0:dmsetup: underlying device, REQ_FLUSH: not supported, REQ_FUA: not supported
  kernel: kvdo0:dmsetup: Using write policy sync automatically.
  kernel: kvdo0:dmsetup: loading device 'vdo_test'
  kernel: kvdo0:dmsetup: zones: 1 logical, 1 physical, 1 hash; base threads: 5
  kernel: kvdo0:dmsetup: starting device 'vdo_test'
  [...]
  systemd[1]: dev-mapper-vdo_test.device: Job dev-mapper-vdo_test.device/start timed out.
  systemd[1]: Timed out waiting for device dev-mapper-vdo_test.device.
  systemd[1]: Dependency failed for /data_dir.
  systemd[1]: data_dir.mount: Job data_dir.mount/start failed with result 'dependency'.
  systemd[1]: Dependency failed for File System Check on /dev/mapper/vdo_test.
  systemd[1]: systemd-fsck@dev-mapper-vdo_test.service: Job systemd-fsck@dev-mapper-vdo_test.service/start failed with result 'dependency'.
  systemd[1]: dev-mapper-vdo_test.device: Job dev-mapper-vdo_test.device/start failed with result 'timeout'.
  [...]
  

• Similar issue is not observed for smaller vdo device of size ~10 GB.