Stripe width is a "minimum" value. So fi you have it set to 5 and then lower it to 1 there's no need to changes as you are meeting the requirement of 1 stripe at minimum.
Thanks for clarifying. After playing a bit more last night I deduced that its just a minimum setting.
But it still seems out of compliance IMO. Stripe width in my view is - Use set # of spindles..
Lets say you've had 5 stripes on handful of VMs then introduced more VMs. Now stripes are not helping - disks maxed IO. Large stripe size causing more issues than benefit.
So reduce policy width to 1 on VMs, but still find your VMs IO are still hitting 5 disks?
What I discovered is if I temp change a VM to a cache reserve policy of above 0 and SW=1, it will trigger rebuild, While VM is rebuilding I set to VM to different policy of Cache=0 , SW=1, and the VM continues to rebuilt back to 1 stripe without cache reserve. Meaning don't have to wait for cache reserve policy to complete rebuilt before setting to back to SW=1 cache=0 policy.