This post is more than 5 years old
24 Posts
0
1603
Tdev size
I believe when we create tdev and do not bind to any pool, it should be in Global memory. What will be the size of unbound tdev (eg 100GB)?
Thanks,
Shailender
This post is more than 5 years old
24 Posts
0
1603
I believe when we create tdev and do not bind to any pool, it should be in Global memory. What will be the size of unbound tdev (eg 100GB)?
Thanks,
Shailender
Top
codyhosterman
286 Posts
0
November 12th, 2013 15:00
TDEV cache usage used to be somewhat of a straight up equation, but is now a much more complex algorithm that allows for much greater efficiency. So it is not really something that can be answered here. Contact your EMC account team as they will have tools that can help you with cache sizing and usage.
Quincy561
1.3K Posts
0
November 11th, 2013 11:00
Size of the TDEV does not change when it is bound vs. un-bound. It simply is made ready when it has a pool for storage.
Shailender_cho1
24 Posts
0
November 11th, 2013 14:00
If this is the case, where that tdev will be created till its unbound?
Shailender_cho1
24 Posts
0
November 11th, 2013 14:00
If we create five 200 GB tdev and forget to add to pool, will that occupy complete global memory?
Quincy561
1.3K Posts
0
November 11th, 2013 14:00
Same place as after it is bound to a pool, global memory.
seancummins
226 Posts
0
November 11th, 2013 15:00
No, just its metadata will reside in global memory (no different than any other volume). You won't be able to store any real data on it until it has been bound to a pool.
Sent from my iPhone
Shailender_cho1
24 Posts
0
November 11th, 2013 18:00
What is the size of that metadata? It should be in bytes or kilobytes. How to calculate that size? I want this information for capacity planning.
Shailender_cho1
24 Posts
0
November 12th, 2013 15:00
May I please get answer to my question?
Anonymous User
67 Posts
0
February 1st, 2014 05:00
Hello Shailender.
A TDEV would use 143 KB of cache and an additional 8 KB of cache for every GB of reported device size.
Refer to page 19, "Best Practices for Fast, Simple Capacity Allocation with EMC Symmetrix Virtual Provisioning Technical Note".
hope this helps.
thanks.
codyhosterman
286 Posts
0
February 3rd, 2014 09:00
This 143 KB statement is no longer accurate (as of 5875) and as such this statement was removed from the document. It is now a far more flexible algorithm.