Maybe the session is TF/Mirror Emulation (symmir) and not TF/Clone (symclone)? Issue "symclone list" and "symmir list" and see if either of those show the session.
yes, knowledgebase - it's available at support.emc.com.
the discover is also likely hanging due to the lock on the SYMAPI database file. the discover tries to update the database, but will fail due to another process already having a lock on it.
The devices are not locked. As the error message states, there is a lock on the SYMAPI database. This is usually a result of a process not exiting cleanly and leaving a semaphore lock on the database. Run a search on the error message in the knowledgebase and you'll see multiple solutions for working around this or correcting it.
That would be expected. The SYMCLI_WAIT_ON_DB variable tells the command to keep running, waiting for the other process to release the lock before executing and taking the lock itself. Given that the process that left the lock on the DB file is probably something that exited abmormally, the lock is not going to get released unless it is done manually.
Take a look at KB article 13263 (support.emc.com/kb/13263). It shows you how you can tell what process is holding the lock/handle on the database file so you can try to see if it's a process that can be terminated.
Anonymous User
242 Posts
2962
0
Posted October 24th, 2013 08:00
Standard device is a 2-way mir
and BCV device is a raid 5 bcv decvice
Solution Enable on ESX and VM are different.