Increasing Disk Space for KVM Guest hit error "device-mapper: remove ioctl on loop0p1 failed: Device or resource busy"
(Doc ID 2736040.1)
Last updated on AUGUST 22, 2023
Applies to:
Exadata Database Machine X8-2/X8M-2 Hardware - Version All Versions to All Versions [Release All Releases]Linux x86-64
Symptoms
Attempt to increase disk space for KVM Guest "/u01" in X8/X8M Exadata rack by following the steps in Exadata Maintenance Guide ~ Section "Increasing the Disk Space in a Guest" getting this error ::
# /opt/exadata_ovm/vm_maker --create --disk-image /EXAVMIMAGES/pv3_vgexadb.img --size 100G
[INFO] Releasing loop device /dev/loop0...
[INFO] Removing device maps for /dev/loop0...
[INFO] Running 'kpartx -d -v /dev/loop0'...
[EXCEPTION] internal error: The command 'kpartx -d -v /dev/loop0' returned with exit status 1.
Command standard output is ''.
Command error output is 'device-mapper: remove ioctl on loop0p1 failed: Device or resource busy <<<<<<<<<<<<<<<<<<
'.
# dmsetup ls
VGExaDbDisk.pv2_vgexadb.img-LVDBDisk (252:12) <<<<<<<<<<<<<<
From vm_maker.log we can see this ::
[2020-12-09 08:47:12 -0500][EXCEPTION][/opt/exadata_ovm/vm_maker][exception][DISPLAY][] internal error: The command 'blkid /dev/VGExaDbDisk.pv2_vgexadb.img/LVDBDisk -s TYPE' returned with exit status 2. <<<<<<<<<<<<
Command standard output is ''.
Command error output is ''.
[2020-12-09 09:57:24 -0500][ INFO][/opt/exadata_ovm/vm_maker][remove_loop_device][DISPLAY][] Releasing loop device /dev/loop0...
[2020-12-09 09:57:26 -0500][ INFO][/opt/exadata_ovm/vm_maker][log_indent][DISPLAY][] Removing device maps for /dev/loop0...
[2020-12-09 09:57:26 -0500][ INFO][/opt/exadata_ovm/vm_maker][log_indent][DISPLAY][] Running 'kpartx -d -v /dev/loop0'...
[2020-12-09 09:57:26 -0500][EXCEPTION][/opt/exadata_ovm/vm_maker][exception][DISPLAY][] internal error: The command 'kpartx -d -v /dev/loop0' returned with exit status 1. <<<<<<<<<<<<
Command standard output is ''.
Command error output is 'device-mapper: remove ioctl on loop0p1 failed: Device or resource busy <<<<<<<<<<<<
# lvscan
ACTIVE '/dev/VGExaDb/LVDbTmp' [3.00 GiB] inherit
ACTIVE '/dev/VGExaDb/LVDbVarLog' [18.00 GiB] inherit
ACTIVE '/dev/VGExaDb/LVDbSys2' [15.00 GiB] inherit
ACTIVE '/dev/VGExaDb/LVDbVar1' [2.00 GiB] inherit
ACTIVE '/dev/VGExaDb/LVDbSwap1' [16.00 GiB] inherit
ACTIVE '/dev/VGExaDb/LVDbHome' [4.00 GiB] inherit
ACTIVE '/dev/VGExaDb/LVDbSys1' [15.00 GiB] inherit
ACTIVE '/dev/VGExaDb/LVDbVar2' [2.00 GiB] inherit
ACTIVE '/dev/VGExaDb/LVDoNotRemoveOrUse' [2.00 GiB] inherit
ACTIVE '/dev/VGExaDb/LVDbVarLogAudit' [1.00 GiB] inherit
ACTIVE '/dev/VGExaDb/LVDbExaVMImages' [1.46 TiB] inherit
ACTIVE '/dev/VGExaDbDisk.pv2_vgexadb.img/LVDBDisk' [100.00 GiB] inherit <<<<<<<<<<<<<<<<
[root@npx02cn01-adm ~]# losetup -a
/dev/loop0: [64522]:268447782 (/EXAVMIMAGES/GuestImages/kvmguest.localhost.com/pv2_vgexadb-1.img.old (deleted)) <<<<<<<<<<<<<<
Changes
Increase disk space for KVM Guest
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 |
Changes |
Cause |
Solution |