Extended LUN size is not reflected in Guest VM (DomU)
(Doc ID 2371574.1)
Last updated on SEPTEMBER 08, 2022
Applies to:
Oracle VM - Version 3.4.1 and laterOracle Cloud Infrastructure - Version N/A and later
Information in this document applies to any platform.
Symptoms
- LUN directly connected to a Guest VM (DomU) is extended in the storage array;
- Oracle VM Manager shows correctly the new LUN size, after refreshing it via the Storage tab;
- Guest VM (DomU) does not detect new disk size
- multipath -ll does not show correct new size on Oracle VM Server , command 'fdisk -l' and/or 'lsblk' might show correct LUN's size
Example (taken from an Oracle VM Server):
multipath -ll
360002ac00000000000000036000030b1 dm-74 3PARdata,VV
size=900G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw <--- WRONG SIZE!
'-+- policy='round-robin 0' prio=130 status=active
|- 1:0:0:39 sdao 66:128 active ready running
|- 1:0:1:39 sdcd 69:16 active ready running
|- 2:0:0:39 sdds 71:160 active ready running
'- 2:0:1:39 sdfh 130:48 active ready running
fdisk -l
Disk /dev/sdao: 1503.2 GB, 1503238553600 bytes
Disk /dev/sdcd: 1503.2 GB, 1503238553600 bytes
Disk /dev/sdds: 1503.2 GB, 1503238553600 bytes
Disk /dev/sdfh: 1503.2 GB, 1503238553600 bytes
lsblk
sdao 66:128 0 1.4T 0 disk
sdcd 69:16 0 1.4T 0 disk
sdds 71:160 0 1.4T 0 disk
sdfh 130:48 0 1.4T 0 disk
Cause
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
Symptoms |
Cause |
Solution |
References |