Jeffrey Mohler wrote:
Ya...I wouldn't get near reallocation that you really =dont= need, given the CPU and disk use, and secondary effects that will add to your system.
I agree. reallocate start -o -a <aggr_name> is *not* pleasant. Very impactful to the protocol latency in the system no matter how much iron you have in the heads and/or backend
However, if you don't have FSR on, and would really like to turn it on, you have no other choice really but to first run reallocate -A once...
Free space frag is only an issue, if it's an issue...and disk that 'not-busy' is soaking up the additional IO from it cleanly, and without any of the other secondary effects of fixing a problem that ain't there.
Well put. I agree.
/M
Work on the actual problem. Alignment...if it does exist as an issue, it chews up CPU, chews up disk IO, and makes the CP process slow and latent to client ACKs.
Jeff Mohler mailto:jmohler@yahoo-inc.com Tech Yahoo, Storage Architect, Principal (831)454-6712 YPAC Gold Member Twitter: @PrincipalYahoo CorpIM: Hipchat & Iris