Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

tutil0 - ATT1 lock on volume - may i vxmend?

Created: 02 Jul 2012 • Updated: 03 Jul 2012 | 3 comments
This issue has been solved. See solution.

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)
 

Comments 3 CommentsJump to latest comment

Gaurav Sangamnerkar's picture

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

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

SOLUTION
Gaurav Sangamnerkar's picture

To know more on how to clear tutil & putil flags

 

http://sfdoccentral.symantec.com/sf/5.0/hpux11iv3/...

 

http://www.symantec.com/docs/TECH15609

 

A similar problem what you faced:

 

https://www-secure.symantec.com/connect/articles/r...

 

Gaurav

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

Wannes P's picture

Thanks very much!

Released the lock, and resumed my vxevac. worked without problems.

 

Thanks for the additional resources