Highlighted

Cannot unbind volume because it is a Copy Session source/target

Jump to solution

We have two meta volumes on my VMAX 40K that I cannot unbind / dissolve / delete because they are being used as a Copy Session source or target, see error below:

symconfigure -cmd "unbind tdev XXXX from pool <POOL>;" prep

A Configuration Change operation is in progress. Please wait...

    Establishing a configuration change session...............Established.

    Error occurred while Defining change number 1:

    Cannot use the device for this function because it is a Copy Session source

    Device XXXX generated the failure

    Terminating the configuration change session..............Done.

The configuration change session has failed.


symdev show XXXX

<removed several lines>

Extent Based Clone     : Source

<removed several lines>

We have not knowingly created any copy sessions.  These two volumes are no longer in use.  How can we clear the copy or extent based clone session so we can remove these volumes?


Thanks in advanced

Labels (1)
0 Kudos
1 Solution

Accepted Solutions
Highlighted
3 Argentum

Re: Cannot unbind volume because it is a Copy Session source/target

Jump to solution

Were these devices presented to VMware servers at one time? These may be stuck VAAI sessions... if you open a case with EMC Support, the PSE lab should be able to dial-in and clear them.

View solution in original post

7 Replies
Highlighted
7 Thorium

Re: Cannot unbind volume because it is a Copy Session source/target

Jump to solution

run symdev show on that device and look at its pairing ..if you see another device, add them to a file and run symclone terminate

0 Kudos
Highlighted
3 Argentum

Re: Cannot unbind volume because it is a Copy Session source/target

Jump to solution

Were these devices presented to VMware servers at one time? These may be stuck VAAI sessions... if you open a case with EMC Support, the PSE lab should be able to dial-in and clear them.

View solution in original post

Re: Cannot unbind volume because it is a Copy Session source/target

Jump to solution

Yes, these were ESX datastores that are no longer needed.  We have unmounted and detached them from all the ESXi hosts already.  Is there a command we can issue to release stuck VAAI sessions or do we need the PSE?

Regarding the symclone suggestion, I don't see any pairing information in the symdev output but we have done symclone list and that returns "No Copy sessions found".

0 Kudos
Highlighted
3 Argentum

Re: Cannot unbind volume because it is a Copy Session source/target

Jump to solution

You'll need a PSE for this one.

0 Kudos
Highlighted
3 Argentum

Re: Cannot unbind volume because it is a Copy Session source/target

Jump to solution

Yeah, if it is indeed a stuck VAAI XCOPY session you will need to engage PSE. You can check though by doing a symdev show on the device and seeing if there is a session listed in the "Extent Based Clone" field. If there is a hung session it may list as "Target" or "Source". The symdev list -held command can sometimes expose this too.

Note that both of these may prove negative but a VAAI session could still persist as occasionally Solutions Enabler may be cleared of the session, but Enginuity still has a hung session but not reporting it correctly to SE. So there can be false negatives in SE with this method, but if it lists something in Extent Based Clone you can be sure that is the issue.

0 Kudos
Highlighted
4 Tellurium

Re: Cannot unbind volume because it is a Copy Session source/target

Jump to solution

was this device expanded recently using protect bcv option?

0 Kudos
Highlighted

Re: Cannot unbind volume because it is a Copy Session source/target

Jump to solution

The problem was a hung XCOPY VAAI session.  The day after I opened the case, our account SE called to say there is a code upgrade to fix an issue with snaps and clones that can result in hung sessions that should also fix hung VAAI sessions.  He recommended we upgrade to 5876.163.105.

0 Kudos