I am interested specifically in the MCSC piece of this conversation. I have tried and failed to expand a eagerzerothick vmdk while the cluster is running via CLI due to file locks. now I could shutdown both nodes of the cluster and expand the vmdk no problem but that defeats the purpose of a cluster where the only downtime you take is the time it takes to failover.
Could you possibly introduce a -L lunreset into your eagerzerothick expand command in step 5 and get the expansion to start running without downtime. My guess is that if that would even work(which I doubt) you would be stuck waiting for the 0′s to be written before the clustered servers could do anything with the volume.
would love to hear your thoughts
Nate
↧
By: Nate Klaphake
↧