"Plex in volume is locked by another utility" reported when attempted to run a "vxplex" command
Article ID: 100000493
Updated On:
Description
Error Message
vxvm:vxplex: ERROR: Plex in volume is locked by another utility
Resolution
When this error is seen, it is normally because a previous operation, such as a plex attach operation, never completed, hence the message "locked by another utility".
As long as vxtask list
or a listing of the process table does not show a task already running for the volume, the utility fields which VERITAS Volume Manager (VxVM) uses as a locking mechanism, can be cleared.Use the vxprint
command to display the TUTILO and PUTILO (temporary and persistent utility fields respectively) of a volume:# vxprint -g
# vxprint -g rootdg testvol1
Note that the "TUTILO" flag is set for both volume and the plex. This flag must be cleared from both volume and plex.
TYNAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 v testvol1 fsgen ENABLED 614400 - ACTIVE ATT1 - pltestvol1-01 testvol1 ENABLED 615330 - ACTIVE - - sddisk04-01 testvol1-01 ENABLED 205110 0 - - - sddisk04-03 testvol1-01 ENABLED 410220 205110 - - - pltestvol1-02 testvol1 ENABLED 615330 - ACTIVE ATT - sddisk03-03 testvol1-02 ENABLED 615330 0 - - - Note that the "TUTILO" flag is set for both volume and the plex. This flag must be cleared from both volume and plex.
This can be done using:
# vxmend -g clear all ...
For this example, the following would be run:
# vxmend -g rootdg clear all testvol1 testvol1-02
Use the vxprint command
# vxmend -g
For this example, the following would be run:
# vxmend -g rootdg clear all testvol1 testvol1-02
Use the vxprint command
again to verify the cleared states.The vxplex
command previously attempted should now work.
Issue/Introduction
vxvm:vxplex: ERROR: Plex in volume is locked by another utility
Was this article helpful?
Yes
No
Powered by
