I am a little confused about what space QTS actually uses to store snapshot metadata. And what else unallocated space is needed/used for with Thick/Thin volumes. You can reserve space within the volume provisioning, or - according to my understanding of the documentation - QTS might also start saving this metadata on unallocated portions. I think this is why, when you don't go with a static volume size, QTS is so in-your-face about leaving unallocated space (ie, the threshold warnings, default set at 80% - 20% is a lot to leave on the table). Ideally I would like to have a small 2-3TB volume for personal backup with snapshots giving extra roll-back functionality. Then a large 10TB or so static volume for media, etc. But I'm still uncertain how to properly accomplish this. Right now, it's with two Thick volumes maxed out, with the smaller having internal-volume reserved space for snapshots. But I am worried that the stability of the system will be compromised if I allocated 95%+ of the space (though not sure if this is a valid concern).
Also, with Thick volumes (with preset volume sizes, unlike Thin) why would a Threshold warning even be useful unless QTS is silently filling up unallocated space with metadata, etc?
I will probably just end up going the static volume route after playing around with things for a few more days...