Unsolved
This post is more than 5 years old
2 Intern
•
211 Posts
0
5015
September 10th, 2014 03:00
help on " symcfg list -tdev -detail " output
Hi All,
It seems that the device 0FA3 is falling into 2 pools , FC_T1 and ATA_T2, why is the device 0FA3 shown in 2 pools? Is it a thin device or a volume in VMAX? is FC_T1 and ATA_T2 a thin pool or storage group, respectively? Appreciate your guides.
# symcfg list -tdev -detail -dev 0FA3
Symmetrix ID: 1234
Enabled Capacity (Tracks) : 2672912640
Bound Capacity (Tracks) : 2209680
S Y M M E T R I X T H I N D E V I C E S
-------------------------------------------------------------------------------
Pool Pool Total
Flags Total Subs Allocated Written
Sym Pool Name EMSP Tracks (%) Tracks (%) Tracks (%) Status
---- ------------ ----- --------- ----- --------- --- --------- --- -----------
0FA3 FC_T1 FX.. 2209680 0 0 0 1269492 57 Bound
ATA_T2 --.- - - 1269624 57 - - -
Total --------- ----- --------- --- --------- ---
Tracks 2209680 0 1269624 0 1269492 0
emcmagic
2 Intern
•
211 Posts
0
September 10th, 2014 04:00
a thin device can belong to more than one pool! that is new to me.
Now, please help me, how come can a thin device belong to two different type of storages? I thought the thin device will be assigned to a host, then which means the data on it could be located on either FC_T1 or ATA_T2 drives?
KW160
121 Posts
0
September 10th, 2014 04:00
Slight correction. A TDEV can only bound to ONE pool. (You can check the binding with "symdev show"). However if the device is under FAST VP control, data can be moved to any pool that is part of the applied FAST VP policy.
emcmagic
2 Intern
•
211 Posts
0
September 10th, 2014 05:00
Thanks for clarification, KW160!
I noticed that you used FAST VP, not 'FAST". Is that correct only in FAST VP that data on 0F3A (LUN) can be located on different pools, and if in FAST, then it can only located in one pool, since FAST cannot move sub-lun?
sree_98
1 Message
0
September 10th, 2014 21:00
Yeah you tend to use FAST VP for extent wise movement of data across pools (hence we have the tdev showing association with more than one pool in your above output), where as if you use FAST, the entire device will be moved.