07-02-2012 06:04 AM
Hi all,
I have a problem on a server which we are migrating. A vxevac session was CTRL-C'd (for reasons not important), about 10 seconds after launching the vxevac command.
^CCaught interrupt signal
VxVM vxsd ERROR V-5-1-407 Attempting to cleanup after failure ..
Relaunching gives following error:
VxVM vxassist ERROR V-5-1-1225 Volume VOL-SZD-Z01-EDS01-DB_DISK_67 is locked by another utility
VxVM vxevac ERROR V-5-2-3537 Aborting disk evacuation
Now, after migrating all other storage, 2 disks remain, both part of this volume. Output from vxprint:
(ocan2901:/tmp)# vxprint -g DG-SZD-Z01-EDS01 | grep VOL-SZD-Z01-EDS01-DB_DISK_76
v VOL-SZD-Z01-EDS01-DB_DISK_76 fsgen ENABLED 209715200 - ACTIVE ATT1 -
pl VOL-SZD-Z01-EDS01-DB_DISK_76-01 VOL-SZD-Z01-EDS01-DB_DISK_76 ENABLED 209715200 - ACTIVE - -
sd DSK-SZD-Z01-EDS01-9f4f-01 VOL-SZD-Z01-EDS01-DB_DISK_76-01 ENABLED 170230528 0 - - -
sd DSK-SZD-Z01-EDS01-9f5a-01 VOL-SZD-Z01-EDS01-DB_DISK_76-01 ENABLED 39484672 170230528 - - -
(ocan2901:/tmp)# vxprint -g DG-SZD-Z01-EDS01 | grep -i 9f4f
dm DSK-SZD-Z01-EDS01-9f4f xp24k0_9f4f - 170230528 - - - -
sd DSK-SZD-Z01-EDS01-9f4f-01 VOL-SZD-Z01-EDS01-DB_DISK_76-01 ENABLED 170230528 0 - - -
(ocan2901:/tmp)# vxprint -g DG-SZD-Z01-EDS01 | grep -i 9f5a
dm DSK-SZD-Z01-EDS01-9f5a xp24k0_9f5a - 170230528 - - - -
sd DSK-SZD-Z01-EDS01-9f5a-01 VOL-SZD-Z01-EDS01-DB_DISK_76-01 ENABLED 39484672 170230528 - - -
sd DSK-SZD-Z01-EDS01-9f5a-02 VOL-SZD-Z01-EDS01-DB_DISK_84-01 ENABLED 130745856 0 - - -
As you can see, the volume has a temp lock - ATT1.
As no plexes or subdisks are locked, i think it is safe to remove the lock using vxmend. But i am not sure. I am no Veritas expert.
Thanks alot for your help!
Wannes
(ocan2901:/tmp)# modinfo | grep -i vx
35 7be86000 50ca0 301 1 vxdmp (VxVM 5.1SP1RP2P2HF7 DMP Driver)
37 7ba00000 21ce60 302 1 vxio (VxVM 5.1SP1RP2P2HF7 I/O driver)
39 7be84bb0 1198 303 1 vxspec (VxVM 5.1SP1RP2P2HF7 control/sta)
213 7b35f300 d40 304 1 vxportal (VxFS 5.1_SP1RP2 portal driver)
214 7a600000 202170 21 1 vxfs (VxFS 5.1_SP1RP2 SunOS 5.10)
217 7aa4e000 6a3b0 308 1 vxfen (VRTS Fence 5.1SP1RP2)
237 7abe0000 b7a8 305 1 fdd (VxQIO 5.1_SP1RP2 Quick I/O driv)
Solved! Go to Solution.
07-03-2012 01:22 AM
If you are sure that no other tasks are running (in "vxtask list" , it is safe to remove the locks ..
you will need to use "vxmend -g <diskgroup> clear" option to clear the locks ..
Gaurav
07-03-2012 01:22 AM
If you are sure that no other tasks are running (in "vxtask list" , it is safe to remove the locks ..
you will need to use "vxmend -g <diskgroup> clear" option to clear the locks ..
Gaurav
07-03-2012 01:33 AM
To know more on how to clear tutil & putil flags
http://sfdoccentral.symantec.com/sf/5.0/hpux11iv3/html/vxvm_admin/ag_ch_plexes_vm15.html
http://www.symantec.com/docs/TECH15609
A similar problem what you faced:
https://www-secure.symantec.com/connect/articles/recovering-failed-vxevac
Gaurav
07-03-2012 07:27 AM
Thanks very much!
Released the lock, and resumed my vxevac. worked without problems.
Thanks for the additional resources