This post is more than 5 years old
4 Posts
0
1474
October 7th, 2013 06:00
Over an hour to unbind TDEVs
Hello All. I have a question/issue. I have TDEVs in the size of 35gb each, that Iuse to create metas of 68gb, 136gb and 272gb. They are bound to either ATA or fiber channel. While I was reclaiming space, I unmapped the metas and ran an unbind. Then umbner of metas varied. However, they were in excess of 15 for each unbind. While symconfigure said that the command completed successfully, the device went into Not Ready mode, but tey were still bound to the thin pool. It took over an hour for them to no longer be associated to a thin pool. An example of the command I used is below:
symconfigure -sid xxx -cmd "unbind tdev 1000:100a from pool ATA_R6_3;" comm
I've done it from the command line and from within Unisphere. The results were the same, still took over an hour for the dev to be unassociated from the thin pool. I ran that command before the dissolve and after I unmapped the devices. These are STD devices.
Any help is appreciated/
Regards,
Nathan
AranH1
2.2K Posts
0
October 7th, 2013 08:00
If the thin devices in question have allocated tracks from thin pools then after the unbind command completes the system will begin reclaiming the allocated tracks from the thin devices. Once all of the tracks are deallocated from the thin devices they will show as being unbound from the pool. So what you are most likely seeing is the "draining" process of the thin devices.
actwon
4 Posts
0
October 7th, 2013 08:00
Ok. That makes sense. How do I check what thin devices (physical TDATs) a device is spread across? I'm using only Unisphere or SymCLI. If I were still using ECC it would be easy fro me to get that information from the properties of the device. Do I still use symdev?
AranH1
2.2K Posts
0
October 7th, 2013 09:00
Thin devices are spread across every TDAT in the pool, so even if you could see that information in the CLI it would not be helpful. What you can see is how much allocated capacity there is for the TDEV from each pool, and that is the number that will help you understand how much capacity needs to be reclaimed before the TDEV will complete the unbinding process.
You can use the command below to look at the allocation of a TDEV across all pools in the array. So you can see that the device I queried below has 510GB of capacity allocated from a pool that will need to be reclaimed by the pool before the device will complete the unbinding process.
symcfg -sid xxx list -tdev -detail -gb -devs 1bc0
Symmetrix ID: 00019590xxxx
Enabled Capacity (GBs) : 75500.6
Bound Capacity (GBs) : 511.2
S Y M M E T R I X T H I N D E V I C E S
-------------------------------------------------------------------------------------
Pool Pool Total Compressed
Bound Flags Total Subs Allocated Written Size/Ratio
Sym Pool Name ESPT GBs (%) GBs (%) GBs (%) GBs (%)
---- ------------ ----- ---------- ----- ---------- --- ---------- --- ---------- ---
1BC0 TP_2TB_R6 F..B 511.2 2 510 100 0.0 0 510.9 0
TP_600G_R5 -.-- - - 0 0 - - 0.2 0
TP_100EFD_R5 -.-- - - 0 0 - - 0.0 0
Total ---------- ----- ---------- --- ---------- --- ---------- ---
GBs 511.2 1 511.2 1 0.0 0 511.2 0
Legend:
Flags: (E)mulation : A = AS400, F = FBA, 8 = CKD3380, 9 = CKD3390
(S)hared Tracks : S = Shared Tracks Present, . = No Shared Tracks
(P)ersistent Allocs : A = All, S = Some, . = None
S(T)atus : B = Bound, I = Binding, U = Unbinding, A = Allocating,
D = Deallocating, R = Reclaiming, C = Compressing,
N = Uncompressing, . = Unbound,