I'm not running any script. I like to know how to do manueally. I'm curious to know what and how i should come out if device or array not acquired a lock.
Not exactly. Some times i got warning as external device lock not acquired or unable to acquire. I know only EMC can lock a array when we need for some critical operations. Like if i want to lock a device (say a volume) what i'm supposed to do. Thats it.
Peri AFAIK we can manage array locks. We can simply query device-level locks. You can have a look at "symdev hold/unhold" commands (and "symdev -held list") but I guess it isn't what you are looking after.
device locks are only taken by solutions enabler when they are needed, if you are having trouble getting a device lock then there is another process running that has taken the lock to prevent you from interfering with it's operation and it will be released when that operation is complete.
If you need to find out what process has taken the lock you can run symdev list -lock -sid xxx against the array, you will see a time held column on one of the right hand columns, this is in seconds so you can work back from current time to see exactly when the lock was taken out. If you are curious to dig deeper you can check the symaudit logs on the array to find out what host was running the commands at that time. e.g.
symaudit -sid 692 list -v -symdev_range 01de:01de -start_date 2/5/2010
You will get lots of information regarding the operations.
Record Number : 14718 Records in Seq : 1 Offset in Seq : 1 Time : 05/02/10 21:46:36 Vendor ID : EMC Corp Application ID :
Application Version : 8.1.3.33 API Library : SEK API Version : V7.1.0.0 (Edit Level: 1008) Host Name : ENGXP OS Name : WinNT OS Revision : 5.1.2600Se Client Host : Process ID : 00004700 Task ID : 00007892 Function Class :
Action Code :
Text :
Username : H:MGMTHOST1\PMARTIN
Activity ID : SE1edf07ac98
This should give you plenty of information to figure out why you are seeing locks on your devices. down to the OS and user that did the operation that took the lock pertaining to the time you are looking at.
HankDorsett
66 Posts
0
October 1st, 2009 08:00
Peri1
20 Posts
0
October 1st, 2009 09:00
MikeMac1
2 Intern
•
292 Posts
0
October 5th, 2009 11:00
Are you trying to manually lock a device? And if so, why? Trying to get a better understanding of your question.
MikeMac
Peri1
20 Posts
0
October 5th, 2009 12:00
Regards,
Peri
xe2sdc
4 Operator
•
2.8K Posts
0
October 6th, 2009 07:00
You can have a look at "symdev hold/unhold" commands (and "symdev -held list") but I guess it isn't what you are looking after.
Peri1
20 Posts
0
April 29th, 2010 13:00
Sorry for delayed reply. I liked to know whether symapi_db locked manually. If then how?
You are right that "symdev -held list" will lists symmetrix devices in the device group that have holds for a timefinder/snap session.
Boom1
131 Posts
0
April 29th, 2010 14:00
EMC gives reserve option to get ownership.
if device can not get external lock and if we do it manually, it will not resolve our problem.
because configuration process try to lock it again.
rawstorage
3 Apprentice
•
423 Posts
0
May 5th, 2010 08:00
Peri,
device locks are only taken by solutions enabler when they are needed, if you are having trouble getting a device lock then there is another process running that has taken the lock to prevent you from interfering with it's operation and it will be released when that operation is complete.
If you need to find out what process has taken the lock you can run symdev list -lock -sid xxx against the array, you will see a time held column on one of the right hand columns, this is in seconds so you can work back from current time to see exactly when the lock was taken out. If you are curious to dig deeper you can check the symaudit logs on the array to find out what host was running the commands at that time. e.g.
symaudit -sid 692 list -v -symdev_range 01de:01de -start_date 2/5/2010
You will get lots of information regarding the operations.
Record Number : 14718
Records in Seq : 1
Offset in Seq : 1
Time : 05/02/10 21:46:36
Vendor ID : EMC Corp
Application ID :
Application Version : 8.1.3.33
API Library : SEK
API Version : V7.1.0.0 (Edit Level: 1008)
Host Name : ENGXP
OS Name : WinNT
OS Revision : 5.1.2600Se
Client Host :
Process ID : 00004700
Task ID : 00007892
Function Class :
Action Code :
Text :
Username : H:MGMTHOST1\PMARTIN
Activity ID : SE1edf07ac98
This should give you plenty of information to figure out why you are seeing locks on your devices. down to the OS and user that did the operation that took the lock pertaining to the time you are looking at.
I know of no way to take out these locks at will.