Creating file system on nvmeotcp devices is failing

Issue

• Creating file system on nvmeotcp devices is failing

nvme-subsys2 - NQN=nqn.19xx-11.com.dell:PowerMax_Cronus:00:000xxxxx0298
\
 +- nvme2 tcp traddr=172.16.11.107 trsvcid=4420 live
 +- nvme3 tcp traddr=172.16.11.108 trsvcid=4420 live
 +- nvme4 tcp traddr=172.16.21.107 trsvcid=4420 live
 +- nvme5 tcp traddr=172.16.21.108 trsvcid=4420 live

# multipath -ll mpathb
mpathb (eui.0298xxxxx03544390000xxxx00012020) dm-3 NVME,EMC PowerMax_Cronus
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=50 status=active
  |- 2:18439:1:1497   nvme2n1  259:0   active ready running
  |- 3:19463:1:1497   nvme3n1  259:28  active ready running
  |- 4:18440:1:1497   nvme4n1  259:56  active ready running
  `- 5:19464:1:1497   nvme5n1  259:84  active ready running


# mkfs.ext2 -v /dev/mapper/mpathb
mke2fs 1.46.2 (28-Feb-2021)
fs_types for mke2fs.conf resolution: 'ext2'
Warning: could not erase sector 2: Input/output error
warning: 160 blocks unused.

Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1313280 inodes, 5242880 blocks
262144 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
160 block groups
32768 blocks per group, 32768 fragments per group
8208 inodes per group
Filesystem UUID: 67c1dc54-7464-48a2-b00e-535f21e1e028
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000

Allocating group tables: done
Warning: could not read block 0: Input/output error
Warning: could not erase sector 0: Input/output error
Writing inode tables: done
Writing superblocks and filesystem accounting information: mkfs.ext2: Input/output error while writing out and closing file system

Nov  9 08:01:15 hostname kernel: blk_update_request: critical target error, dev nvme1n11, sector 6144 op 0x3:(DISCARD) flags 0x4a00 phys_seg 1 prio class 0
Nov  9 08:01:15 hostname kernel: blk_update_request: critical target error, dev dm-13, sector 6144 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Nov  9 08:01:15 hostname kernel: blk_update_request: critical target error, dev nvme2n12, sector 6144 op 0x3:(DISCARD) flags 0x4a00 phys_seg 1 prio class 0
Nov  9 08:01:15 hostname kernel: blk_update_request: critical target error, dev dm-14, sector 6144 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Nov  9 08:01:44 hostname kernel: nvme nvme3: starting error recovery
Nov  9 08:01:44 hostname kernel: nvme nvme1: starting error recovery
Nov  9 08:01:44 hostname kernel: nvme nvme0: starting error recovery