![]() So they will continue to try and write data, while your actual storage space might be full because all three vmdk's (or just one of them) have experienced growth using all available space. The OS on the VM is not aware that the partition (your c drives for example) is thin provisioned. Because all those 3 disk will try to write their data upto 400GB. When your environment grows rapidly you will end up with overprovisioned storage. On a 447GB datastore you may also create, for example, 3 thin provisioned vmdk's. But you won't have any issues regarding corrupting data. So on a 447GB DS you may for example create one vmdk that is 400GB thick provisioned. Thick provision means you actually allocate the storage on a Datastore. Thin Provision is fine, but you would have to somehow monitor growth of the DS. Because that would fill up the DS immediately. If you have a 400GB DS I would recommend not to put a 400GB thick provisioned disk on there, for obvious reasons. It can do this up to a maximum of 320GB of your C drive plus the 80GB that is still sitting somewhere. If the amount of data grows because you put a 100GB file on your C: drive, the amount of data written on the DS grows to 115GB. In your case that seems to be 15GB and that is the amount of data actually written on the DS. In this case, what is relevant, is the amount of data in use. When it comes to actual storage allocation in a thin provisioned situation the 320GB is not very relevant. This means that in Windows you have a 400GB partition to use, if you want to make a 320GB C:\ drive out of that, that is up to you. The size of the added vmdk is the provisioned size, in this case thin provisioned. VSphere7 in HTML5 client should show the actual size with an option to inflate if it is a thin disk. If actual size is important to you, like allocated space on the DS and provisioned space for the VM should be equal, then I simply wouldn't use Thin Provision in the first place. I cannot fully determine if the disksize we are looking at in you attachment is the actual size or the provisioned size. Personally I would guess this is a sparse file and that it is almost empty, except for the 15GB. However in your VM folder you might see this VMDK of 400GB. When you choose thin provisioning it only allocates the space on the DataStore that is actually in use, thus around 15GB. This means that within the operating system of the VM you can add a disk upto 400GB in size. Results The selected storage policy becomes the default policy for the datastore. From the list of available storage policies, select a policy to designate as the default and click OK. In the Default Storage Policy pane, click Edit. Click the Configure tab, and click General. With thin provisioning you can create a vmdk with an x amount of storage for a vm, let's say in your case 400GB. Procedure In the vSphere Client, navigate to the datastore. I am not quite sure of all the details here, but looking at first glance I would guess it has to do with the disk being Thin Provisioned.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |