[ PCA / OVM ] The Size of a New LUN on Server is Incorrect If an Existing LUN Is Unmapped First
(Doc ID 2207373.1)
Last updated on JULY 14, 2020
Applies to:Oracle VM - Version 3.0.1 and later
Private Cloud Appliance - Version 1.0.1 and later
Oracle Cloud Infrastructure - Version N/A and later
This document attempts to clear what is meant with "LUN ID"in the Oracle VM release notes when stating :
If a LUN belonging to an unmanaged Fibre Channel array is unmapped from a server and a new target is mapped to it using the same LUN, then after rescanning the physical disks on that server, the size of the new LUN is set to the size of the LUN that was unmapped.
Remapping LUNs is risky because it can data corruption since the targets have been switched outside of the server. An error should appear in the messages file:
Warning! Received an indication that the operating parameters on this
target have changed. The Linux SCSI layer does not automatically adjust
Workaround: Ensure that when exposing a new target, you do so with a LUN that has not previously been used since the last reboot.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document