Error 2201: Server_2 : unable to acquire lock(s)

Question

I am testing VMWare's SRM and when I try to failback to the protected site I get the above error. It is a result of the following command:

server_export server_2 -Protocol nfs -o anon=0 access=IP:IP:IP /Filesystem

What do I have to do prior to failback so that the SRA stops reporting this error?

Rainer_EMC · Answer

I'll see if I can find someone familiar with the plugin to answer

kensagle · Answer

Have you tried the command again?  It could be the trying to run during the NASDB backup. Sagle

bstuart1 · Answer

I tried it twice yesterday, I will put humpty back together and try it again this afternoon.

bstuart1 · Answer

I tried again today. Same result.

kchuemc · Answer

Hi! The 'Server_2 : unable to acquire lock(s)' error could be caused by a few different factors, such as some partition on the Control Station being full, or some other process holding the locks... I'd recommend opening a support case to get the lab to check it out. Kelvin

SAMEERK1 · Answer

Hi,

The nasdb backup process is not the only process that causes the above message. A best practice is to always check which locks are preventing you from executing the commands.
The /nas/lock/ directory should be checked for any existing locks. Clear the relevant locks as follows, but be careful that the locks are not valid locks . This has to be decided on a per-case basis.
Change directory: cd /nas/lock and /nas/lock/db

To list out any locks:

ls -l

Get an octal dump of the locks, which gives the process ID that is holding the lock:

od -d *

This will give you an idea of what is holding the lock. If the process is slot_recover, the Data Mover may be in the process of failing over, so be careful:

ps -ef |grep

Run: kill (where pid is the process ID associated with the lock. If necessary, use kill -9 as root user.)
Use caution when killing a process.

Sameer

nandas · Answer

I 'll personally prefer to open a service request and run it by our Support Personnel to check and clear the lock on the NASDB. As already stated the lock may be for different reasons or may be for some hung or incomplete processes - so better to get it checked by support personnel.

My 2 cents

Thanks,
Sandip

Celerra

Error 2201: Server_2 : unable to acquire lock(s)

Was this post helpful?