Right now the OnApp Storage keeps allocating vdisks to hard drives until it is full. The problem with this is that when a client starts to add data, they will run into FS issues since the physical hard drive is full. Some will say, "disable the overcommit" when creating the datastore...then what is the purpose of thin-provisioning when you can't over commit in the first place? Not being able to use overcommit and thin-provisioning on expensive SSD's is extremely expensive.
OnApp needs to rebalance the vDISKs as the actual physical hard drives fill up. If a client starts using more disk space, OnApp needs to spread the vdisk on physical drives that have space available. If this does not happen, clients will run into FS crashes and corruption once the physical drives fill up. This needs to be an automated process.
Please sign in to leave a comment.