Question of thin provision

Similar Questions

• Question about thin provisioned disks

  I did some searching but can't find specific answers, I need and I apologize in advance if these questions are public knowledge. I know also my setup is very small compared to most houses VMWare normally using these forums, but we are moving slowly in the 2nd Decade of the 21st century (or try).

  I have a new install ESXi 5 and move during one ESX3 host that has about a dozen of VMs on it.  I recently built vCenter host servers and my future view connection server.  I'm kind to vCenter again as my previous installation of ESX 3 was a single server and us were not investing in the vCenter at the time option (missed a lot of features and ease of upgrade during this transition, but 20/20 declining).  I'm a little green in using vCenter so take pitty on my ignorance.

  It's more time than I wanted to and I just want to know the best way to change these 2 servers (recently built and configured systems Win 2008 R2) to thin provisioned disks.  I need to keep all the storage space I can and beyond the obvious problem of being able to provide more space than you physically, I have no problem to do so (in addition to get them changed).  If there are negatives I'm missing, please report them to me.  The possiblities that I see are:

  The clone and thin provision then delete the originals.

  Use the stand-alone converter on them (from above).

  Completely rebuild thin provisioned with disks.

  If someone can give me a quick list of possible problems and pitfalls for these opportunities or to get to a better suggestion, please do so and thanks in advance.

  Manual of Clark

  PRIMOS Inc.

  Since you have storage vMotion the clone or standalone VMware converter are both viable options.   Not sure about the disadvantages of these options.

  You didn't say what kind of server it is, but I'm always careful about the cloning of the domain controllers.   Without the option for storage vmotion I rebuild a DC from scratch.

  Post edited by: mittim12

• Considerations, concerns or questions RE Thin Provisioning.

  Hey all,.

  I have a question about a provisioning.  It seems that we have a debate about our team on the issue of whether we should use it as a policy.

  We have a cluster 2 ESX 4.0 and ESX 3.5 environment all connected to EMC via NFS storage.

  What should concern us, is there on the virtual computer performance problems if the storage starts to develop?  Should do us as a global policy or a policy according to the needs?  Can someone shed some light on this?

  Hello.

  The biggest concern with a provisioning is that you have to manage it.  It is still something to keep an eye on.  Implementation of the alarms is the key, if you have vCenter.  For the workloads highest performance, there will be some additional latencies involved.  The thin disks will not work with VMware FT either.

  Good luck!

• Thin provisioning question

  Tonight

  We recently P2V. by 4 Dell servers that all went well.

  When it came to thin provisioning of storage, we encountered a slight impediment. No matter what we do, we cannot recover any space with a provisioning.

  For example, we have only one server, 62 GB C. We have done the following:

  Defragmented

  CHKDSK would be

  SDelete - c (and even z, followed by another - c)

  Then migrate to another store of data configured as thin. We seem to get 0 space back even if Windows reports being 31.6 GB of free disk space.

  Don't get me wrong in the past doing the 4 steps above still retrieved the free space, but just this time on all 4 servers, we cannot recover anything.

  I have even converted to thick, and then to thin in case something to be funny.

  With the help of ESX 4 fully patched on all hosts. The only thing I can think is that when we thin put in service in the past, we were running ESX 4 with no patches and we have recently updated to the current version, but I can't really believe that a fix/update would have broken something as Basic.

  Any idea?

  There is a very simple solution for this problem, I found a couple of weeks ago.

  Do the usual "sdelete - c C:" stuff, and then migrate as Thin put in service in a store of data with a * different blocksize *.

  Then it just works how it has always been.

  It's only when you migrate it to a store of data with the same size block, it's broken.

  --

  Jules

  [email protected]

  www.Jules.FM

• Default MARVIN and Thin Provisioning storage policy

  Hello

  When you use the default storage of MARVIN to vSAN on our new Evo strategy, it seems that all VMs are thick provisioned, not thin.

  My question is, why has it chosen default thick provisioning provisioning method for the storage of MARVIN policy? My understanding of vSAN vanilla is that a provisioning is the default value. I plan to create a new storage for provisioning strategy, but first of all, I would like to understand if thick is preferred on the Evo and, if so, why?

  Thanks in advance.

  It's quite strange - because by default in Evo must be a provisioning is not thick...

  The Evo has to ship to the QEP with the same default values as VSAN. As the team of VSANS, we would recommend thin provisioning...

  Can you confirm that the policy is set to thick. Maybe a screenshot of the policy upgrade...?

  This could be a factory error, or maybe a change not verified by a rogue administrator?

  Can I ask who is the partner of QEP. It may be useful if you send (using posts here) what is Device Evo... (you'll find this under 'health' in the user interface of Evo, next to the health of system - ID is probably something like MAR12345604...

  Kind regards

  Mike

• New-VM cmdlet always deploys "Thin-provisioned" VMs - need help

  Hi all

  I am at a total loss on this and spent several days trying to figure out what's wrong.  I'm deploying a new virtual machine from a template using PowerCLI version 5.1 Release 1.  The model is thin-set as all our models are, but when you specify my "New - VM" command, the resulting virtual machine always deploys as thin-provisioned even if I specify "thick".  Here is the command I use:

  PowerCLI C:\ > New-VM-model $templatename - $datastoreClustername - DiskStorageFormat EagerZeroedThick - $hostname - VMHost Datastore name $newVMname - location $foldername

  The above command returns the following error that 'EagerZeroedThick' is not a valid for the parameter - DiskStorageFormat option (although I see it clearly is done by "Get-Help-detailed New - VM")...:

  New - VM: 20/02/2014 12:09:18 new - the specified invalid VM storage format. Valid values are "Thin" and "thick".

  Online: 1 character: 7

  + New-VM < < < <-Template (model Get - Id VirtualMachine - vm - 1060) Datastore - Orion1_DSCluster - DiskStorageFormat EagerZeroe

  dThick - VMHost orion2esx01.cisco.com - name rcdn6-vm91-8-location "generic user (jstest).

  + CategoryInfo: InvalidArgument: (:)) [new-VM], InvalidArgument)

  + FullyQualifiedErrorId: Client20_VMServiceImpl_GetnerateCloneSpec_IvalidStorageFormat, VMware.VimAutomation.ViCore.Cmd

  lets.Commands.NewVM

  So I try the same command above, but this time by using 'thick ':

  PowerCLI C:\ > New-VM-model $templatename Datastore thick - VMHost $hostname - DiskStorageFormat - $datastoreClustername - name $newVMname - location $foldername

  The above command will successfully deploy a new virtual machine to the specified model, but the resulting virtual machine will always be Approvisionnés Thin rather than thick as I said...

  I have Google had the devil on this issue and did not happen to something that helps me...  I tried all the combinations of parameters, and the parameter order hoping that would be the thing without result.  As I said, I am at a complete loss and hope someone here can point me in the right direction.

  Sum, my 2 questions are:

  1. Why is EagerZeroedThick not considered as a valid option for the setting -DiskStorageFormat even if "Get-Help-detailed New - VM" clearly states that it is?  (I've seen a lot of example online of people using this option as well)
  2. Why the new virtual machine being deployed as a thin-put in service of the virtual machine, even if I specify thick for the setting -DiskStorageFormat of New - VM?

  It is a 1 vCenter/vSphere 5.1 update environment.

  Thanks in advance for your help.

  I finally received a response from the Vmware Support on this topic and thought I'd share it for anyone else running in this issue:

  VMware support:

  "I confirmed and discovered that it is a bug that is already running of our public relations team that suits him.

  And confirmed that this will be fixed in the next major release of VMware CLI power.

  And now, there is no ETA for it but I think would it as well as ESXi 5.5 U1 version but I can't confirm it. »

• Save space on the disc thin provision

  Hello.

  I have a virtual machine that has thin provisioned N. 3 disks:

  • 1-> provisioned size 20 GB
  • 2nd-> size 3 GB provisioned
  • 3-> provisioned size 20 GB

  If I look on the use of the storage on the server ESXi 5 (VI client) I see this:

  

  But if I connect on the virtual computer, I see this:

  

  With a simple calculation, I don't see that really used on the virtual machine storage size is only (20 - 8,64) + (3-0, 746) + (20 - 5,46) = 28,15 GB.

  Very different 40,48 GB storage used .

  The question is:

  is it possible to reclaim unused storage space?

  In other words: is it possible to align the "storage used" showed on the resources of the ESXi server to that actually used from the VM?

  Thanks in advance.

  You can use vmkfstools with the option ofpunchzero to recover the disk space of the thin configured virtual disks. To do this, you must first set to zero unused space within the OS itself invited, then turn off the virtual machine and run the vmkfstools command.

  André

• Ability to store data when thin provisioned

  Hi all

  VSphere 4.1 running in a cluster of two hosts, this cluster uses a Dell Equalogic PS4000 SAN for storage.

  Confusion I have is with thin configured data stores and my Exchange Server (2010) - running on MS Server 2008 R2 Ent.

  Exchange server uses three data warehouses on the San, one for the OS, one for data and one for newspapers.

  The data of databases store is the one that gives me problems, it has been defined as thin provisioned 750 GB, when I look on the SAN & via VCenter he said 90% full until she went to 100% after the SAN sent several alerts - the virtual machine then crashed with out-of-space error.

  To cut a long story short, I have twol questions

  (1) in this case why the SAN & VMWare say the data store is full, BUT when I connect to the virtual Windows computer it was about 50% in use?

  (2) when the data store that contains the databases filled I don't understand Exchange has fallen more but why why the crash of the VM?  The OS data store still had plenty of free space.

  I got this error by increasing the space of 100 GB to 850 GB data store while the virtual machine is very well (even if Windows was complaining to a stop suddenly unexpected).

  Thanks in advance for your help.

  K

  And without perspective, as it was put in service end and touch 750 GB, 300 GB, then was removed, it would not 750Go because it may not decrease in size - is that correct?

  (This would answer why the SAN says he uses 750Go of 750 GB, but Windows thinks there ish 300 GB free).

  Yes, that's correct... the recovery of unused/dead/removed space don't is not automatically made.

• Thin Provisioning LUNS and virtual disks

  Hi all

  I recently came across a problem with our VMware View environment, where in vCenter about 20 of our virtual office message that there is no more space left. When I looked at the data warehouses that store with my clones related, they have both said more than 200 GB of free space.

  In an attempt to clarify the environment, but do not go off-topic, some of our pools view are configured to give each virtual desktop a disposable disc service end of 4 GB (Temp and swap files). I noticed that in vCenter, the question asked to VMware for more memory space pointed to these disposable disks.

  I was with the support of a few hours... on the side of EMC Clarion, LUN (which are thin provisioned) also showed full... but VMware support was able to create a 1 GB file on the data store that was full according to the Clarion.

  We sent EMC our papers and they were back and just said the table is fine, the LUN was out of space... but this does not explain to me why vSphere showed the LUN as having 200 GB free. EMC said they did not know and I need to talk with VMware. I'm confused, if the LUN was not always full, how we were able to create the 1 GB file on the data store?

  Curiously, all the desktop computers that do not have the disk of 4 GB disposable were very well... they had no problem. I'm almost thinking, perhaps disposable disc was full of temp and file exchange and that where this problem started, but I can't seem to be able to confirm that the 4 GB.

  Another thing is, began to be blocked on this data store, even if these virtual desktops, have been removed from the files. I'm unable to delete records in the data store. I know that I can restart the hosts to unlock, but let's just delete this store of data/lun individual completely.

  I was wondering if anyone has had similar problems or has any advice?

  Mike

  Teas because there are 2 parts of the area of thin provisioning.

  When you create a thin LUN on the side of the table, regardless of the size, it only * affects * about 1 GB (for Clariion).  Like many parts of this LUN if written, it allocates more.

  Now when you create an om VMFS file, unless you use eagerzeroedthick (which you're not), there still, not all these data in a 1 GB (10GB or other) is actually hit or written to the creation time.  Thus, the table side only sees (for example) hit 16 MB.  Now to delete some files on the side of VMFS.  The table does not know that those "affected" blocks are now free (because VMware doesn't have the ability to communicate that back to the table), so it independently as always in use.  As a result, you end up with a shift of how is used according to the table, and the file system.

  So now consider a 500 GB LUN, who think that the painting is "full", but said VMFS has 200 GB of free.  That 200 GB was probably written at a time in its history, then deleted.  Thus, full to the table, but not the file system.  When you create small files, VMFS is overwhelming the space previously used, which the Board considers acceptable, but as soon as you try to use the space that is not be 'recycled', it barfs, because its out of space on the backend.

• Thin provisioning / "right-size" database disk

  OK, so I have the setting permissions and ready to deploy to the device.  I don't want to have a 200 + GB DB hard.  I know they say there is a special way, using the OVFTool application if you are using vSphere 4.0.  We run vCenter 4.1 and 4.1 ESXi hosts.  To specify the hard size I want, will it still thinly provision the device with the OVFTool?  I'm looking for clarity in this before deploying the machine, because I will be setting LUN space based on drive of 75 GB database (with room for future growth in LUN).  I apologize if this has already been covered, but I didn't see any other posts related to my question.

  virtualhudak,

  Technically, you should be prevented to deploy the virtual appliance CapacityIQ on a LUN with only 125 GB of free space on the disk.

  You need a data store with at least 258 GB free space on the drive in order to deploy the appliance CapacityIQ. That you complete the deployment wizard, two of the questions asked are if you want the first disk to be configured as a disk, thin or thick. and the same question for the second disk (/ data).

  Once you have deployed the virtual appliance successfully, you can follow the steps to reduce the size of the second (/ data) disk.

  James Ang | VMware engineering
  VMware vCenter operations
  VMware vCenter CapacityIQ
  VMware Capacity Planner
  VMware vCenter Guided Consolidation

• Thin Provisioning does not work or unable to find space?

  Hello

  I have about 30 virtual machines using thin provisioning format. I found 1 especially with a 20 GB drive, TYPE THIN and 19.9 GB used. I entered in the console, check use of space inside the linux and it has 90% free. It uses only 2 GB.

  My question is why not taking advantage of the thin provisiong as other virtual machines. Any ideas?

  Post edited by: vmroyale to remove the PLUGS all THE of the subject line

  Fill the empty space with zero and do svmotion with thin disk as target, it should reclaim the unused space.

  It's how recover you for example 10 gigabytes of Linux root fs

  DD if = / dev/zero/foo bs = 10240 count = 1 M

  RM foo

  then svmotion

  Tomi

  http://v-reality.info

• ESXi 4 Thin Provisioning

  Hello, we have before us to enter the world of virtualization, and am currently evaluating 4 ESXi and vSphere (on the right, the only host for the moment with local 400 GB SAS (RAID10) drives).

  I have a computer configured to drive Thin Provisioning virtual. The hard disk settings show that a currently stocked 10 GB size:

  

  Yet, the summary of the resource for this machine shows 11FR as being currently configured:

  And, more annoyingly / important that the disparity that above, if I try to copy a file of 1.8 GB on this machine, it runs out of space. This raises two questions:

  (1) why it would run out of space when 11 - 7.82 = 3.18 GB is theoretically available?

  (2) even if it did run on space should not commissioning it automatically allocate more space, so this does not happen? As you can see there is lots of space available in the data store.

  I would appreciate a lot of the answers / advice you can offer as despite many VMWare reading guides I can't fothom this one out.

  Thank you

  Sqwim

  What is the disk in Windows within the virtual machine? How freespace do you have here?

  Daniel

  ---

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Thin provisioning alert

  Hello
  Is it possible to put an alarm on overuse datastore (Thin Provisioning)?
  Kind regards
  Ronald

  Hello Ronald.
  Space in metric data (Thin Provisioning) store service is not perceived by the current collector agent (I think that you will need to create a custom script agent to recover). Most likely will be available in the new version of the collector agent in the next version of vFogight.
  Concerning

• ESXI 5.1 "the disc is not thin-provisioned" after copying to the new data store vmdk

  I wanted to create an external backup as a 2nd VM ready-to-run on the 2nd data store.

  I've removed all snapshots, stop the machine virtual and exported the OVF file to a computer, adjusted to the size of the original virtual machine starts in Gparted to update the partition and restart. All very well.

  I then tried to deploy the OVF in the data store alternative (235GB slim, thickness according to the deployment of 250 Wizard). I tried both thick and thin but the error message "cannot deploy the OVF. The operation was cancelled by the user.

  I then manually downloaded the VMDK & OVF file to the 2nd data store and tried to inflate but then received the message "a specified parameter was not correct. The disc isn't thin provisioned. ».

  It seems I have dealing with the same thing, as this is the document here (http://pubs.vmware.com/Release_Notes/en/vsphere/55/vsphere-vcenter-server-55u3-release-notes.html).  However, I have no idea what to do now... and I'm worried because it seems that my backup plan may not work if I can't restore an OVF/VMDK from a disk of visas.

  The solution to the first problem here: https://communities.vmware.com/message/2172950#2172950 that solved my problem 2nd too.

• How to recover free space on Thin provisioned VM

  Hello

  We are trying to recover the thin provisioned VMDK using below UNMAP commands on esxi5.5 update1 host but get error backup volume not supported for UNMAP and we can see that delete also not taken in charge and all status by checking the ATAS list his indicates that the plugin is not loaded we use IBM SVC (VMW_SATP_SVC VMW_PSP_FIXED placeholder (not loaded plugin)

  Let know us how to load the VMW_SATP_SVC plugin to the ESXi 5.5 update1 host and also suggest how to recover free space on thin provisioned VMs

  Here's the output of command, we checked and we suggest to conduct thorough on this

  **************************************************************************************************

  ~ # esxcli storage vmfs unmap-l NONPROD-DS01

  Backup volume 5390312 a-1f3a16fd-b578-5ef3fc1eb0bb devices do not support undo the MAPPING

  *************************************************************************************************

  *******************************************************************************************************

  ~ # esxcli central storage peripheral vaai situation get naa.60050768018105ced80000000 d

  CF 00010

  1. NAA.60050768018105ced8000000000010fc

  VAAI Plugin name:

  ATS status: supported

  Clone status: supported

  Zero status: supported

  Delete status: unsupported

  ********************************************************************************************************

  ********************************************************************************************************

  ~ # esxcli storage nmp ATAS list

  Description of default name PSP

  -------------------  -------------  --------------------------------------------                                                -----------

  Tables VMW_SATP_ALUA VMW_PSP_MRU nonspecific media that use the Protocol AL AU

  VMW_SATP_MSA VMW_PSP_MRU placeholder (not loaded plugin)

  VMW_SATP_DEFAULT_AP VMW_PSP_MRU placeholder (not loaded plugin)

  VMW_SATP_SVC VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_EQL VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_INV VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_EVA VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_ALUA_CX VMW_PSP_RR placeholder (not loaded plugin)

  VMW_SATP_SYMM VMW_PSP_RR placeholder (not loaded plugin)

  VMW_SATP_CX VMW_PSP_MRU placeholder (not loaded plugin)

  VMW_SATP_LSI VMW_PSP_MRU placeholder (not loaded plugin)

  Non-specific bays of VMW_SATP_DEFAULT_AA VMW_PSP_FIXED Supports active/active

  VMW_SATP_LOCAL VMW_PSP_FIXED direct support of connected devices

  ************************************************************************************************************************

  Hi friend

  I checked with the storage provider and they confirmed that the storage system (currently no products support midsize or SVC SCSI unmap commands used by space VAAI claim.)