Troubleshooting
Problem
chdev -dev hdisk command fails when trying to change the reserve_policy attribute on a VIOS SAN disk.
Symptom
$ chdev -dev hdisk# -attr reserve_policy=no_reserve Some error messages may contain invalid information for the Virtual I/O Server environment. Method error (/usr/lib/methods/chgdisk): 0514-062 Cannot perform the requested function because the specified device is busy.
Cause
The error means the hdisk# is currently in use.
Environment
VIOS 2.2 or 3.1
Diagnosing The Problem
Determine what is currently using the hdisk#.
Resolving The Problem
There are a couple of options to consider in order to change the hdisk attribute.
Option 1: Make the change to the ODM only. Then reboot the VIOS at your earliest convenience for the change to take effect:
$ chdev -dev hdisk# -attr reserve_policy=no_reserve -perm
$ shutdown -restart
$ chdev -dev hdisk# -attr reserve_policy=no_reserve -perm
$ shutdown -restart
Option 2: If a VIOS reboot is not possible, determine what is currently using the hdisk, so you can free it up in order to make the change.
For example, if the hdisk is part of a user volume group:
1) The volume group will need to be deactivate (in order to release the hdisk and avoid the "device is busy" error).
2) Retry chdev command (without -perm option)
3) Then bring the volume group back online.
1) The volume group will need to be deactivate (in order to release the hdisk and avoid the "device is busy" error).
2) Retry chdev command (without -perm option)
3) Then bring the volume group back online.
Or if the hdisk is virtualized to a client:
1) The VSCSI disk path will need to be disabled on the client.
2) Put the VTD name associated with the hdisk# in defined state (on the VIOS) to release the hdisk.
3) Retry chdev command (without -perm option).
4) Make the VTD back available (cfgdev).
5. Re-enable the VSCSI disk path on the client.
1) The VSCSI disk path will need to be disabled on the client.
2) Put the VTD name associated with the hdisk# in defined state (on the VIOS) to release the hdisk.
3) Retry chdev command (without -perm option).
4) Make the VTD back available (cfgdev).
5. Re-enable the VSCSI disk path on the client.
For assistance determining what is using the hdisk, contact your local IBM SupportLine Representative and be ready to provide a VIOS snap.
Document Location
Worldwide
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"Component":"","Platform":[{"code":"PF002","label":"AIX"}],"Version":"VIOS 2.2 and 3.1","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]
Was this topic helpful?
Document Information
Modified date:
20 October 2021
UID
ibm11074424