This post is more than 5 years old
2 Intern
•
220 Posts
0
1672
May 20th, 2009 08:00
VDEV devices
Hi
The back end director information is missing for the VDEV device configuration.
Sample output:
============
Device Physical Name : Not Visible
Device Symmetrix Name : 132B
Device Serial ID : N/A
Symmetrix ID : 00019010xxxx
Vendor ID : EMC
Product ID : SYMMETRIX
Product Revision : 5772
Device WWN : 60060480000190102504533031333242
Device Emulation Type : FBA
Device Defined Label Type: N/A
Device Defined Label : N/A
Device Sub System Id : 0x000B
Cache Partition Name : DEFAULT_PARTITION
Device Block Size : 512
Device Capacity
{
Cylinders : 9295
Tracks : 139425
512-byte Blocks : 17846400
MegaBytes : 8714
KiloBytes : 8923200
}
Effective Device Geometry: N/A
{
Sectors/Track : N/A
Tracks/Cylinder : N/A
Cylinders : N/A
MegaBytes : N/A
KiloBytes : N/A
}
Device Configuration : VDEV (Meta Member,
Non-Exclusive Access)
............................
.............................
Back End Disk Director Information
{
Hyper Type : Virtual
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
}
So where this VDEV will get the capacity. Here Vdev is not associated to any back-end director for disks.
Message was edited by:
MikeMac
Removed Symm S/N
The back end director information is missing for the VDEV device configuration.
Sample output:
============
Device Physical Name : Not Visible
Device Symmetrix Name : 132B
Device Serial ID : N/A
Symmetrix ID : 00019010xxxx
Vendor ID : EMC
Product ID : SYMMETRIX
Product Revision : 5772
Device WWN : 60060480000190102504533031333242
Device Emulation Type : FBA
Device Defined Label Type: N/A
Device Defined Label : N/A
Device Sub System Id : 0x000B
Cache Partition Name : DEFAULT_PARTITION
Device Block Size : 512
Device Capacity
{
Cylinders : 9295
Tracks : 139425
512-byte Blocks : 17846400
MegaBytes : 8714
KiloBytes : 8923200
}
Effective Device Geometry: N/A
{
Sectors/Track : N/A
Tracks/Cylinder : N/A
Cylinders : N/A
MegaBytes : N/A
KiloBytes : N/A
}
Device Configuration : VDEV (Meta Member,
Non-Exclusive Access)
............................
.............................
Back End Disk Director Information
{
Hyper Type : Virtual
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
}
So where this VDEV will get the capacity. Here Vdev is not associated to any back-end director for disks.
Message was edited by:
MikeMac
Removed Symm S/N
0 events found
No Events found!


Quincy561
1.3K Posts
0
May 20th, 2009 08:00
This should all be explained in the product guides for Virtual Snap.
John
Quincy561
1.3K Posts
1
May 20th, 2009 08:00
The physical storage it uses is the SAV pool devices.
naren23-3_uew
2 Intern
•
220 Posts
0
May 20th, 2009 08:00
What is SAV pool devices.
How we can determine where the information is stored for the Vdev devices.
Can you refer some documents about the capacity utilization of VDEV devices.