Prior to the "allocation by policy" feature, you would be correct. When this feature is enabled, the new allocations can come from the bound pool, or any other pool in the FAST policy if FAST thinks they would be a better choice based on the workload.
And for tracks already allocated, overwrites will not move the tracks.
for a new write that will allocate new extents , where these new extents will be allocated (on original Thin Pool where the tdev is bounded ) or where ?
and for
overwriting an extents that already allocated and promoted to different thin pool than the thin pool where the tdevv where bounded ,?
Read miss gives the highest scores to read miss for FAST VP promotion, but back-end write activity will also increase scores for promotion with FAST VP.
Quincy561
1281 Posts
514
0
Posted December 7th, 2014 07:00
Prior to the "allocation by policy" feature, you would be correct. When this feature is enabled, the new allocations can come from the bound pool, or any other pool in the FAST policy if FAST thinks they would be a better choice based on the workload.
And for tracks already allocated, overwrites will not move the tracks.