I am curious about 5.32 (INYO) and how it will handle a pool that was expanded while on 5.31. I see plenty of information regarding the restriping of a pool that is expanded while running on 5.32 but how does it handle a pool that was created and then expanded while on 5.31.
We had an issue with an over-subscribed pool (oversubscribed on IO capacity and space capacity) that was expanded to add spindles to the pool. Being on 5.31 we didn't really gain any additional IO/s benefits, we only alleviated the space constraints.
If I take this array up to 5.32, will the pool be rebalanced or does it apply only to expansions performed on the array while it's running on 5.32.
The only relevent command I can find in the 5.32 command line reference is Naviseccli storagepool xxxxx - rebalance but this only displays the rebalancing % complete.
The pool that has been expanded is homogenous (600GB 10k FC disks) and it's not licensed for FAST VP. What I'm looking for is how to kick off this rebalance.
Will the pool properties within Unisphere display a progress of the rebalance effort or will I need to run NAVISECCLI -REBALANCE against the pool? Is there any priority that can be set on the rebalance or can I find out how long the rebalance will take?
This image shows a single pool of 33 4+1 groups that was expanded (before we knew that we wouldn't gain any I/O benefits). I will update to the new Flare, expand this pool again by a single 4+1, and cross my fingers.
Mabro1
2 Intern
•
666 Posts
794
0
Posted September 4th, 2012 09:00
This discussion is now located in the VNX Support Forum.