Creation of xfs file system fails with persistent memory (PMEM) and NVMe over fibre channel configuration on the same system

Content

While running mkfs.xfs over NVMe over fibre channel (nvme-over-fc) devices,  the following errors 
are seen in the log:

mkfs.xfs /dev/mapper/mpathe1
meta-data=/dev/mapper/mpathe1    isize=512    agcount=4, agsize=327680 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=1    bigtime=0 inobtcount=0
data     =                       bsize=4096   blocks=1310720, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
Discarding blocks...Done.
[  398.577211] nvme nvme0: NVME-FC{0.3}: io timeout: opcode 1 fctype 224 w10/11: x00500818/x00000000
[  398.578459] blk_update_request: I/O error, dev nvme0n3, sector 5244952 op 0x1:(WRITE) flags 0xca00 phys_seg 2 prio class 0
[  398.578490] device-mapper: multipath: 253:16: Failing path 259:8.
[  398.578526] nvme nvme0: NVME-FC{0}: transport association event: transport detected io error
: 253:16: Failing path 259:11.
[  428.658376] nvme nvme1: NVME-FC{1}: transport association event: transport detected io error

Workaround
You can disable the PMEM in the system configuration. The fix is in kernel code on PowerPC.

Fix Outlook
The fix will be in RHEL 8.6 z-stream and RHEL 8.7.

I/O device impacted
None.