This message was deleted.
# _general
s
This message was deleted.
o
🤔 Why would you want that? Even outside of Citrix/VMware integration, thin provisioned storage has been the standard for a while now
m
I get that you might want to do this for performance reasons but it’s not a fantastic idea as it’ll eat up a ton of space and ideally this disk is the last thing you want to hit anyway after RAM
j
Its not performance reasons, there is a preference to have one fat volume for BaseDisks and Cache. Our support teams can not make a judgement on how much space there is when doing a Machine Catalogue update, due to the dynamic nature of the cache disks. Too many outages so far, making them full fat will allow them to assess free space. Storage system can take care of the white space / capacity.
m
outages due to running out of disk space?
j
yep, e.g :- they see 150gb free - do a MCS update which creates another 100gb base disk. few hours later, the diff disks have grown and the volume runs out of space.
thick provisioning would have prevented that, can't rely on common sense
m
You can split off your storage pools so your differencing disks don't end up with your master images
I get the problem but I really don't think thick provisioning is the solution there
💯 1