Oracle VM/Oracle Linux Virtualization Manager: Newly Allocated LUN not Scanned as DMM Device if Previously Deleted LUNs Mapper were not Flushed (Doc ID 2770423.1)

Last updated on SEPTEMBER 09, 2022

Applies to:

Symptoms

A newly allocated LUN (sample page83 ID 38a00465<uuid A>) is not visible in multipath monitoring list after proper scsi-rescan:
# multipath -ll | grep -A10 38a00465<uuid A>
#

However the SCSI devices are indeed discovered:
# for i in $(ls /dev/sd*); do echo $i && scsi_id --whitelisted $i; done
(snip)
/dev/sdab
38a00465<uuid A>
/dev/sdcd
38a00465<uuid A>
/dev/sdef
38a00465<uuid A>
/dev/sdgh
38a00465<uuid A>

From same multipath monitoring list, above four block devices are associated with another LUN:
3514f0c5<uuid B> dm-N <product>,<vendor>
size=100G features='1 queue_if_no_path' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| '- 1:0:0:491 sdab 65:528 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| '- 2:0:0:491 sdcd 70:1168 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| '- 3:0:0:491 sdef 71:1616 active ready running
'-+- policy='round-robin 0' prio=1 status=enabled
'- 4:0:0:491 sdgh 8:2112 active ready running

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.