Can you please post output of this commands:

symdev -sid 760 show 0080
symdev -sid 760 show 0EDB

ThX!

C:\>psexec \\emcl001d symdev -sid 760 show 0080 | more

E
rocesses remotely
Copyright (C) 2001-2007 Mark Russinovich
Sysinternals - www.sysinternals.com



Device Physical Name : Not Visible

Device Symmetrix Name : 0080
Device Serial ID : N/A
Symmetrix ID : 000xxxxx0760

Attached VDEV TGT Device : N/A

Vendor ID : EMC
Product ID : SYMMETRIX
Product Revision : 5671
Device WWN : 60060480000xxxxx076047544B303830
Device Emulation Type : FBA
Device Defined Label Type: N/A
Device Defined Label : N/A
Device Sub System Id : 0x0007
Cache Partition Name : N/A

Device Block Size : 512

Device Capacity
{
Cylinders : 37180
-- More -- symdev exited on emcl001d with error code 0.
Tracks : 557700
512-byte Blocks : 35692800
MegaBytes : 17428
KiloBytes : 17846400
}

Device Configuration : BCV (Non-Exclusive Access)

Device is WORM Enabled : No
Device is WORM Protected : No

SCSI-3 Persistent Reserve: Disabled

Dynamic Spare Invoked : No

Dynamic RDF Capability : None

STAR Mode : No
STAR Recovery Capability : None
STAR Recovery State : NA

Device Service State : Normal

Device Status : Ready (RW)
Device SA Status : N/A (N/A)

Mirror Set Type : [Data,N/A,N/A,N/A]

Mirror Set DA Status : [RW,N/A,N/A,N/A]

Mirror Set Inv. Tracks : [0,0,0,0]

Back End Disk Director Information
{
Hyper Type : Data
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [05C, C, A]
Disk Director Volume Number : 195 (0xC2)
Hyper Number : 7
Disk Capacity : 285902m
Disk Group Number : 1
}

BCV Pair Information
{
Standard (STD) Device Symmetrix Name : 0ED3
Standard (STD) Device Serial ID : Not Visible
Standard (STD) Device Group Name : Not/Grouped
Standard (STD) Composite Group Name : Not/Grouped

BCV Device Symmetrix Name : 0080
BCV Device Serial ID : Not Visible
BCV Device Associated Group Name : Not/Associated
BCV Device Associated CG Name : Not/Associated

BCV Device Status : Ready (RW)

State of Pair ( STD < \ > BCV ) : SplitNoInc
Time of Last BCV Action : N/A

State of BCV Mirrors : Synchronized

BCV State Flags : (AllReady)

Number of Inv. Tracks for STD Device : 0
Number of Inv. Tracks for BCV Device : 0
}
-----------------------------------------------------------------------------------------------------

C:\>psexec \\emcl001d symdev -sid 760 show 0edb | more

ocesses remotely
Copyright (C) 2001-2007 Mark Russinovich
Sysinternals - www.sysinternals.com



Device Physical Name : Not Visible

Device Symmetrix Name : 0EDB
Device Serial ID : N/A
Symmetrix ID : 000xxxxx0760

Attached BCV Device : N/A

Attached VDEV TGT Device : N/A

Vendor ID : EMC
Product ID : SYMMETRIX
Product Revision : 5671
Device WWN : 60060480000xxxxx076047544B454442
Device Emulation Type : FBA
Device Defined Label Type: N/A
Device Defined Label : N/A
Device Sub System Id : 0x0007
Cache Partition Name : N/A

Device Block Size : 512

Device Capacity
-- More -- symdev exited on emcl001d with error code 0.
{
Cylinders : 37180
Tracks : 557700
512-byte Blocks : 35692800
MegaBytes : 17428
KiloBytes : 17846400
}

Device Configuration : 2-Way Mir (Meta Member,
Non-Exclusive Access)

Device is WORM Enabled : No
Device is WORM Protected : No

SCSI-3 Persistent Reserve: Disabled

Dynamic Spare Invoked : No

Dynamic RDF Capability : RDF1_Capable

STAR Mode : No
STAR Recovery Capability : None
STAR Recovery State : NA

Device Service State : Normal

Device Status : Ready (RW)
Device SA Status : Ready (RW)

Front Director Paths (2):
{
----------------------------------------------------------------------
POWERPATH DIRECTOR PORT LUN
--------- ---------- ---- -------- ---------
PdevName Type Type Num Sts VBUS TID SYMM Host
----------------------------------------------------------------------
Not Visible N/A FA 08B:1 RW 000 00 019 N/A
Not Visible N/A FA 09B:0 RW 000 00 019 N/A
}

Meta Configuration : Striped
Meta Stripe Size : 960k (2 Cylinders)
Meta Device Members (13) :
{
----------------------------------------------------------------------
BCV DATA RDF DATA
---------------------------- --------------------------
Sym Cap Std Inv BCV Inv Pair R1 Inv R2 Inv Pair
Dev (MB) Tracks Tracks State Tracks Tracks State
----------------------------------------------------------------------
0ED3 17428 - - N/A - - N/A
0ED4 17428 - - N/A - - N/A
0ED5 17428 - - N/A - - N/A
0ED6 17428 - - N/A - - N/A
0ED7 17428 - - N/A - - N/A
0ED8 17428 - - N/A - - N/A
0ED9 17428 - - N/A - - N/A
0EDA 17428 - - N/A - - N/A
--> 0EDB 17428 - - N/A - - N/A
0EDC 17428 - - N/A - - N/A
0EDD 17428 - - N/A - - N/A
0D45 17428 - - N/A - - N/A
0D46 17428 - - N/A - - N/A
----------------------------------------------------------------------
226566 - - - -
}

Mirror Set Type : [Data,Data,N/A,N/A]

Mirror Set DA Status : [RW,RW,N/A,N/A]

Mirror Set Inv. Tracks : [0,0,0,0]

Back End Disk Director Information
{
Hyper Type : Data
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [15C, D, 9]
Disk Director Volume Number : 398 (0x18D)
Hyper Number : 4
Disk Capacity : 285902m
Disk Group Number : 1

Hyper Type : Data
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [06A, C, 9]
Disk Director Volume Number : 155 (0x9A)
Hyper Number : 4
Disk Capacity : 285902m
Disk Group Number : 1
}

Message was edited by:
Stefano Del Corno

Removed SymmID from post.

you mean to say that each i every time i create a BCV for extending any disk,i have to raise a case with EMC for deleting the BCV.

NOTE:Is there anyway that i can extend the disk without using BCV.Will the data be safe.

it's a meta member ..so you would need to unmap and dissolve the meta before you can anything with that device.

No I mean you have to issue a symmir cancel command BEFORE dissolving BCV metavolume.

At least that's what I'd do .. However I never did it thus maybe I'm wrong.

When you expand a meta preserving data, symwin (our software running on the service processor) will use the BCV establishing it with the original metavolume. Once the BCV is synchronized it will host data while the code dissolves existing metavolume and forms a brand new metadevice with old and new members. At the very end of the meta rebuild, symwin will copy data from BCV to the brand new standard volume and give access to the new (bigger) metavolume.

But at the end of the procedure you still have a BCV and its STD device bound in a Timefinder relation.

symdev -sid 760 show 0080 
...
Device Symmetrix Name : 0080
...
Device Configuration : BCV (Non-Exclusive Access)
...
BCV Pair Information
{
Standard (STD) Device Symmetrix Name : 0ED3
...
State of Pair ( STD < \ > BCV ) : SplitNoInc

Thus your BCV device still remember that someone established it to STD device 0ED3 ...
But now device 0ED3 is "bigger" (now it's a 13 member metavolume while the BCV was a 10 member device) ...

As Dynamox said, you can't play with metamembers .. I think you have to open a SR and ask a PSE to clean up wrong BCV-STD relations between STD and BCV members.

Message was edited by:
Stefano Del Corno

You can also "pull" the incorrectly paired BCV from the standard, by pairing the BCV to another standard.

Suppose you have a metadevice consisting of devices 0100 and 0101, and there's a single (non-meta) BCV paired to just device 0100. You can't cancel this relation because of the invalid pairing, but you *can* pair the BCV to another device. This destroys the invalid relation, and then you can cancel the new relation if you want to. Saves you a call to EMC.

(This doesn't appear to work when the invalid BCV happens to be in Synchronized state, though.)

BCV-STD relation sits in BCV GDAT area .. thus establishing a different BCV with your STD will clean symdev output but won't change relations stored in GDAT area of old BCV device..

You are absolutly right ..

Hi,

That's why I wrote: "by pairing the BCV to another standard" instead of: "by pairing the standard to another BCV".

I've used this procedure quite a few times to destroy an invalid relation. Just grab another standard that matches the problematic BCV in size and attributes, and issue a full establish. You'll see that the newly chosen standard "pulls" the BCV out of the invalid relation. You don't even need to dissolve meta's or anything.

I was able to resolve this afetr raising a SR,.The BCV 0088 got mapped to some unwanted FA port.After unmasking it,i tried deleting the BCV & it was Success.

What do you mean with "unwanted" FA port ?? Thus the BCV was really mapped (as stated in symconfigure output) and you had to unmap before being able to delete the volume ??