This post is more than 5 years old
2 Intern
•
220 Posts
0
2026
September 15th, 2010 13:00
Thin Devices(tdevs) in symmetrix
Hi
Normally Thin devices gets storage from thin pools. If thin devices are unbound then that thin device is not part of any thin pools. But it has capacity value.. Please tell me where this thin devices gets the capacity if it not part of thin pool. Below is the sample unbound thin device where it shows capacity value and Thin pool name shows as N/A.
Device Physical Name : Not Visible
Device Symmetrix Name : 1AB6
Device Serial ID : N/A
Symmetrix ID : 001234512345
Number of RAID Groups : 0
Attached BCV Device : N/A
Attached VDEV TGT Device : N/A
Vendor ID : EMC
Product ID : SYMMETRIX
Product Revision : 5874
Device WWN : 00000000000000000000000000000000
Device Emulation Type : FBA
Device Defined Label Type: N/A
Device Defined Label : N/A
Device Sub System Id : 0x0015
Cache Partition Name : DEFAULT_PARTITION
Thin Pool Name : N/A
Device Block Size : 512
Device Capacity
{
Cylinders : 10923
Tracks : 163845
512-byte Blocks : 20972160
MegaBytes : 10240
KiloBytes : 10486080
}
Please let me know if you need further information. I really appreciate your help
Message was edited by: SymmetrixForumsModerator: I modified the WWN and SN.
modaslam
2 Intern
•
217 Posts
0
September 25th, 2010 03:00
well it works fine, since thin was pretty new to me. I forgot the binding step and the Unix team complains there are not able to format the disk. my dev was 17GB, he was ableto see the device size as17GB. I had to complete the binding step and the good part is once the device is bound it will tell you which pool does it bound to.
thin devs only consumes the block once you have bound and start writing to the new blocks, you can grow up to you device capacity like 17GB. once its full you need to add another tdev.
dynamox
9 Legend
•
20.4K Posts
1
September 15th, 2010 14:00
i would think this is just a device definition, it's not actually consuming any space until it's bound to a pool, kind of like VDEVs
emcsanadmin
54 Posts
1
September 16th, 2010 14:00
it is a part of a data device.
dynamox
9 Legend
•
20.4K Posts
0
September 16th, 2010 18:00
not until it's bound to a pool
MP-ZrCrU
3 Posts
1
September 23rd, 2010 17:00
As previously mentioned, TDEV which is not bounded to thin pool is just a definition. By default not bounded TDEV will have NR (not ready) state. It seems though it still can be mapped to FA and masked to host.