According to your picture, you're in a world of hurt on Pool B and not in dramatically better shape on Pool A. It's not a problem if you use all of your pool space if your volumes are fixed size and fully allocated. However, if you are overprovisioned, and nearly out of space, then that is when bad things happen.
You have three different virtual disk groups in your Pool B "standard" tier that are different set sizes and, based on description may be different disk types and capacities. With this setup you will likely experience some performance issues. Ideally, all disks in a tier (standard, performance, archive) should all be the same speed and capacity and they should be added to the pool in set sizes that are consistent.
Also, according to your screen shot, you show 685MB free in your Pool B which is dangerously low if you are overcommitting. If you add up all of the volumes, you have provisioned from the MSA Pool B, are they more than the 10.6TB total size of the pool?
This is going to take some effort on your part. The question is are you just plain using more capacity than you have? If so, order some more disks. Or is the issue that you have deleted stuff that hasn't been zero reclaimed yet? Create a spreadsheet of all your data stores, what volumes those datastores use on the MSA, which pool those volumes are in, and columns for free and used space of the datastore as reported by VMWare.
We can try to help you make sense of that spreadsheet if needed but I think you'll start to get some answers by just going through the exercise yourself.
Best of luck
You have three different virtual disk groups in your Pool B "standard" tier that are different set sizes and, based on description may be different disk types and capacities. With this setup you will likely experience some performance issues. Ideally, all disks in a tier (standard, performance, archive) should all be the same speed and capacity and they should be added to the pool in set sizes that are consistent.
Also, according to your screen shot, you show 685MB free in your Pool B which is dangerously low if you are overcommitting. If you add up all of the volumes, you have provisioned from the MSA Pool B, are they more than the 10.6TB total size of the pool?
This is going to take some effort on your part. The question is are you just plain using more capacity than you have? If so, order some more disks. Or is the issue that you have deleted stuff that hasn't been zero reclaimed yet? Create a spreadsheet of all your data stores, what volumes those datastores use on the MSA, which pool those volumes are in, and columns for free and used space of the datastore as reported by VMWare.
We can try to help you make sense of that spreadsheet if needed but I think you'll start to get some answers by just going through the exercise yourself.
Best of luck
