Virtual disk capacity limit

Similar Questions

• Machine virtual hard disk (virtual disk) of the upper size limit put into service

  Hi there, so I'm trying to create a hard drive or a virtual disk in a Virtual Machine in order to configure the virtual machine as a file server. The data store is a Promise VTrak M610P and I installed the vtrak as a type of VMFS5 5,46 TB of space (4 2 hard disks to each RAID 5). In the virtual machine, I added a hard drive and selected the store data vtrak and tried to set the provisioned to 5.46 TB size and type thick lazy disposition to zero, but I get an error of DiskCapControl with the range values. I changed the size set in service and 4 TB and he accepted the new hard drive. I can't find anything on the actual limit on the creation of hard disk in a virtual computer.

  
  

  I'm running a server Supermicro X7DAL-E with VMware ESXi 5.5 U2.

  Any ideas would be useful. Thank you.
  

  I forgot I asked a similar question on a different section of the forum (shame on me), but I found a solution. Please see the following post Re: SMB access using esxi host and manage with MS server 2008 storage

  Here's what I wrote on the link above:

  So it turns out that there seems to be something wrong with vClient when you add a hard disk (virtual disk) to a virtual machine of size greater than 4 TB. Article VMware KB: value of range error message when you add more than 4 TB capacity discs in vSphere Client describes this if you encounter this problem, add the hard drive via vSphere CLI, CLI power or vmkfstools. So this seems to be a known issue on vClient. What I ended up doing was using vClient, creation of hard disk, adding to the virtual machine (size of the hard drive is to 5.45) and when I would get the error message on the DiskCapControl out of reach, I would just click OK and then finalize the creation of the hard drive on the virtual machine. Once the process is complete, I selected the virtual machine and noticed that he indeed added a new HDD size 5.45 TB even if he's complained about it. I pulled to the top of the virtual machine with windows server 2008 R2 installed and was able to create a new disk under windows and set it up as a shared drive on the network. Looks like vClient must be updated by VMware and correct this bug, if it's a bug that I think. Thank you for the help vervoort!

• Error: the capacity of the disk virtual parent and the child disk capacity are different (67).

  Hello

  I tried to increase the hard drive of a machine space of 10 GB for a 20 GB virtual linux. I closed down the VM, then ssh was in the ESXi server. From there on, I ran the command:

  vmkfstools x 20 G Apatite.vmdk

  The command was executed successfully. Then, when I turned on the virtual machine I had and still do me:

  Reason: The capacity of the disk virtual parent and the child disk capacity are different.
  Cannot open disk ' / vmfs/volumes/503fd5b8-d1cef086-eb4a-10bf487b38db/Apatite/Apatite-000001.vmdk' or one of the snapshot disks it depends on.

  I tried many things such as the cloning of the Apatite.vmdk of Apatite - repaired.vmdk. That works, however, I get an old version of the virtual machine. I do not receive my changes of Apatite - 000001.vmdk or Apatite-000001 - delta.vmdk.

  I have a very important job on my VM that I am restoring. I should have backed up before doing anything else I've done. Now, it seems that I pay the price.

  Can someone help me get my VM? Is it possible to increase the size of the snapshot (Apatite - 000001.vmdk) or reduce the size of the parent so that they match, and the virtual machine start?

  Help, please.

  Thank you

  Apatite - 000001.vmdk
  # Disk DescriptorFile
  version = 1
  Encoding = 'UTF-8 '.
  CID = 79c3c056
  parentCID = cf2ec09b
  isNativeSnapshot = 'no '.
  createType = "vmfsSparse."
  parentFileNameHint = "Apatite.vmdk"
  # Description of the measure
  RW 41943040 VMFSSPARSE ' Apatite-000001 - delta.vmdk.
  # The database disk
  #DDB
  ddb.longContentID = "11ad79de6b5a5fe9218cfd7179c3c056".
  ddb.toolsVersion = "9216.
  modified entries are marked in red
  After you have made the changes - do NOT start the virtual machine
  Instead, remove from inventory and run
  vmkfstools 'Apatite - 000001.vmdk'-i 'consolidated.vmdk' d slim
  When did edit the vmx file and replace
  scsi0:0. FileName = 'Apatite - 000001.vmdk ".
  with
  scsi0:0. FileName = "consolidated.vmdk".
  now, you can save the VM again.

• Reduce the size of the virtual disk RAID 5

  I have Windows Server 2003 is installed on a virtual disk PERC H700 RAID-5. Total size of the disk is 5.5 TB. The problem is that WinServer 2003 cannot use the disk due to the MBR 2 TB limit (and I can't convert to GPT without destroy all partitions, which is what I try to avoid). Since 3.5 TB of drive space is unallocated (and reconciliations), is there a way to reduce the size of the virtual disk to remove this space which can not be used anyway? Then, I could by using the remaining capacity to create a new virtual disk that can be set up as GPT and access the space through it (or two new virtual drives 2 TB and 1.5 TB in size). I know that you can expand a virtual disk, but you can a shrink?

  No, you can develop most of the virtual drives, but you will not be able to reduce them.

  You will have to start on this subject, creating a VD less than 2 TB for boot/OS disk, then the rest can be used in an another VD.

• MD1220 disk expansion & expansion / resize virtual disk

  I seek to add 6 new MD1220 to a current configuration of 6 who are chained together.  Two quick questions on this...

  (1) is there as a limit to how many MD1220 can be connected?

  (2) once the virtual disks were created in all of my original 6 devices, is it possible to resize or add to this Setup?  Or I should blow away and recreate?

  Thank you
  Greg

  Hello Greg,.

  (1) is there as a limit to how many MD1220 can be connected?  You can put a maximum of 4 cases with the MD1220 can be chained together (which gives a total of 96 disks per SAS port).

  (2) once the virtual disks were created in all of my original 6 devices, is it possible to resize or add to this Setup?  Or I should blow away and recreate? You can add disks to your virtual drive and can increase the size, but depending on how much space you add that it can be faster to back up data and then recreate the virtual disk and restore your data.  A virtual disk expansion is really slow and it may take weeks or even months depending on the size of the virtual disk.

  Please let us know if you have any other questions.

• Max MD3000 virtual disk size

  Can how big I grow a virtual disk?  As above, I have two servers Dell PE in a cluster failover with Windows 2008R2 Ent. The MD300 contains two Virtual disks 1 x 50 GB of disk as a cluster quorum and 1 x 4TB which holds virtual machines. I would add 2 TB for the largest virtual disk; that would be appropriate?

  The only limit to the size of the virtual disk on a series of Dell's MD3k is the maximum number of physical drives in a single group. For raid 5, it's 30, RAID 10, is 44 and for raid 0 is 45.

  When you configure a cluster, I usually use a Quorum GB 2. If it is an installation of hyper-v I then use 2 disks or more virtual to spread the i/o load. If not for hyper-v, then the structure of the virtual disk depends on the needs of the application and storage.

• Monitoring of disk capacity

  Hi all
  I have a question about the «left disk space» tracking options I have a mixed environment: two VCs with 100 virtual machines and another 70 physical systems. What I did to monitor everything, was vFogl attached to two VCs and also installed the fglam on all physical systems and created agent winSys for physical systems.
  What I recognized, is the fact that there are different rules to monitor virtual machine and systems with an agent. For VMs, it is the rule "VMW Virtual Machine logical drive fill rated time" and for the agent on the system phys. "ability".
  But I also want to watch the 'capacity' of my virtual machines disk space. Do I have to install the agent on these virtual machines, & fglam also?
  The background of this issue, it is that our IT support team needs to be enlightened (e-mail on mobile phone), if there is a problem with a smaller disk capacity.
  Thanks in advance for your help,
  Patrik

  Patrik,
  Discover the rule of the use of the logical disk VMW Virtual Machine. Looks like what you are looking for, and it is already in the product.
  VMware tools need to installed and updated on the VMs for this to work, as is, how get the operating system of the host ESX and VC info from the virtual machine level.
  If this isn't possible, fglam and one officer of the BONE is your option.
  -Larry

• Consolidation of many to one of the virtual disks?

  Hello world

  I use a XP client inside a Windows 7 host (using 8 workstations).

  In the configuration of my XP virtual machine I previously assigned (of 50 gigabytes) of disk space into separate virtual folders, about 2 GB each, as shown below.

  

  I now want to have a single vmdk file, with the pre-allocated 50 GB of capacity.

  Is it possible that I can achieve this goal, while keeping my VM in tact? For example can I create a second virtual disk, and then use a cloning tool (from the client) BONE to make a copy to the new virtual drive?

  Here, any help will be greatly appreciated.

  Kind regards

  DAVO

  Hello world

  This can indeed be done! Because I started with a scalable, split, virtual disk, there were several steps; Here's the gist of these measures-

  (1) using the vmware-vdiskmanager merge files into a single.

  http://hostilecoding.blogspot.com.au/2013/06/VMware-merge-multiple-VMDKs-into-single.html

  Note: when running this utility do not forget to include the '2' parameter, which refers to the creation of a virtual disk prealloue, otherwise the following steps (use the shrinkvd program will NOT work!).

  Here is a screenshot of the order that worked for me-

  

  (2) add the newly created virtual disk, 'merged.vmdk' to the existing virtual machine, using these installation instructions.

  https://www.VMware.com/support/WS5/doc/ws_disk_add_virtual.html

  (3) remove the existing virtual machine virtual drive

  (4) to start the Virtual Machine (you will probably be asked if you have moved or copied the VM, I responded with "Proposed").

  (Optionally)-rename the virtual disk of "merged" into something else by renaming the files in the ".vmx" and "hard" files.

  (5) using the shrinkvd resize the virtual disk

  http://www.Softpedia.com/get/system/system-miscellaneous/shrinkvd.shtml

  

  Above, note that the first time, I ran the command it failed with the message "ddb.deletable" is the crux of the problem. I just deleted this line in the relevant file "hard" and the command is represented.

  Now, when I boot on my virtual XP I use only 24 GB of space, and I am able to transfer the Virtual Machine to a smaller drive. in this case a 30 Gig old SSD.

  I hope this helps others.

  Kind regards

  DAVO

• Dell virtual disk are larger. You want to increase the size of the data store.

  Hello

  I started the implementation of a server ESXi 5.5 Update 1 this week. I didn't know Dell shipped the server with two virtual disks instead of one. I realized this _apres_ that I had already created the data store and setup a few virtual machines to the breast. I called Dell who sent specific instructions to increase the removal of the second (empty) virtual disk and add it to the main. In the end, I increased the single VD from 2 TB to 3 TB and I want to give the remaining space in my store of data.

  I tried to follow the article here that explains how to do this via the CLI.

  Well, he did not altogether. Fortunately, I was able to recover my datastore my setting start and end sectors to their original numbers. But I'm still left with this almost 1 TB of space that I can not attribute to the data store. After that I reread storage adapters in the client, the new Dell disk size resulted under measurement devices. Click on "increase...". ", generates the following error which led me on the way to the CLI method:

  Call "HostDatastoreSystem.QueryAvailableDisksForVmfs" to object "ha-datastoresystem" on ESXi '[myservername]' failed.

  I will paste my notes that I took everything by jobs. Things have exploded the rails when I put 4 partition size to the largest size. Any help, please?

  ---

  I use that as a guide:

  http://KB.VMware.com/selfservice/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 2002461

  
  

  1 use start hardware device management tools to increase the capacity of additional disk to the device. For more information, commit your hardware provider.

  This has been done. The new size of the virtual disk is 2791,88 GB (TB 2,79188)

  
  

  2. open a console to the ESXi host.

  Pretty simple.

  
  

  3. get the DeviceID for the data store to change.

  ~ # vmkfstools Pei "/ vmfs/volumes/datastore1 / '.

  System file VMFS-5, 60 extending on 1 partition.

  File system label (if applicable): datastore1

  Mode: public

  Capacity 1971926859776 (blocks of files 1880576 * 1048576), 1042688245760 (994385 blocks) prevail, max size of the 69201586814976 file

  UUID: 534e5121 - 4450-19dc-f8bc1238e18a 260d

  Partitions split (on 'lvm'):

  NAA.6c81f660ef0d23001ad809071096d28a:4

  
  

  A couple of things to note:

  a. the device for Datastore1 ID is: naa.6c81f660ef0d23001ad809071096d28a

  b. the number of Partition on the disk is: 4 ' [...]: 4 "»

  c. the prefix, "naa," means "Network address authority" the number immediately after is a single logical unit number.

  4. Enter the amount of disk space available on the data store.

  ~ # df h

  Size of filesystem used available use % mounted on

  VMFS-5 1. 8T 865.4 G 971,1 G 47% / vmfs/volumes/datastore1

  
  

  5 team of the device identifier, to identify the existing partitions on the device by using the partedUtil command.

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  ~ #

  
  

  According to the table in article KB

  4 13711360 3865468766 251 0 - primary #4, type 251 = 0xFB = VMFS, 13711360-3865468766 areas

  | |        |          |   |

  | |        |          |   \---attribut

  | |        |          \---type

  | |        \---se finishing sector

  | \---a starting from sector

  partition \---Numero

  
  

  Also note how the number of section start the old end sector number is + 1.

  
  

  6 identify the partitions that need to be resized and the size of the space to use.

  We want to resize partition 4. I don't really understand the last part of this sentence, however. Read more.

  
  

  7 the number of sector end you want for the target data store VMFS partitions. To use all out at the end of the disc space, remove 1 of the size of the disk in the areas as described in step 5 in order to get the last usable area.

  ESXi 5.x has a command to do this:

  ~ # partedUtil getUsableSectors "/ vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a".

  1 5854986239

  This means that we want 4 Partition of "naa.6c81f660ef0d23001ad809071096d28a" to be:

  13711360 - 5854986239 (i.e. the end of the disc)

  
  

  8 resize the partition containing the target VMFS Datastore using the command partedUtil, specifying the original existing partition and the desired end sector:

  Using the above information, our command is:

  resize # partedUtil ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 5854986239

  
  

  9 step 8, the partedUtil command can report the warning:

  He did not. Displacement.

  
  

  10. the tables of partitions have been adjusted, but the VMFS data within the partition store is always the same size. Now there is an empty space in the partition where the VMFS data store can be grown.

  
  

  11 launch this v vmkfstools command to perform a refresh for VMFS volumes.

  Fact.

  
  

  12 reach the VMFS Datastore in the new space using the command - growfs vmkfstools, specifying the partition containing the VMFS Datastore target twice.

  vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 '.

  
  

  It did not work. I got an error:

  / vmfs/volumes # vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' /vmfs/devices/disks/naa.6c81f660ef0d «»

  23001ad809071096d28a:4 ".

  Cannot get device head way /dev/disks/naa.6c81f660ef0d23001ad809071096d28a:4 information

  
  

  Also the partition was very different to what I asked:

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 1560018942 251 0

  
  

  I fixed it by running these commands:

  ~ # partedUtil resize ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 3865468766

  ~ # vmkfstools v

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  Update:

  Since it was such a new machine, not in active production, we have safeguarded the VMs management off the ESXi host. Then flattened the virtual disk, recreated, and then created a store of data with the right size. (TPG this time, naturally.) We put the management of virtual machines on the data store. For Windows virtual machines, we have restored the using AppAssure. Everything is ok now.

  Need to add a new item to the list of punch: check what Dell has done the configuration of the virtual disks. :-)

• Script to export the virtual disk information in a specific format

  Hi all

  First too all the Scripting Guys who I borrowed the code here, thank you!

  Now, I was able to get all the information I want vcenter but I have problems with two of the scripts I wrote.  It is with regard to obtaining information on the virtual disks associated with all virtual machines in the environment.

  I was able to export the data, but I get a line by VM that does not work for the way in which we want to use the data.

  What I am looking for is a csv export with one line per virtual machine that looks like:

  VM number 1, hard disk number 1 name number 1 datastore, path of vmdk number 1 hd, hd number 1 capactity, number 1 hd, hard drive controller number 2 name,... up to 7

  name of number 2 VM...

  Thank you!

  Alec

  OK, I see what happened.

  The 2nd block is to create empty properties in the object.

  The value should be $null like this

  $report = @()foreach($vm in Get-VM){  $row = New-Object PSObject -Property @{Name = $vm.Name}  $i = 1  Get-HardDisk -VM $vm | %{    $row | Add-Member -Name "Disk #$($i) Name" -Value $_.Name -MemberType NoteProperty    $row | Add-Member -Name "Disk #$($i)" -Value $_.FileName.Split("/")[1] -MemberType NoteProperty    $row | Add-Member -Name "Disk$($i)path" -Value $_.FileName -MemberType NoteProperty    $row | Add-Member -Name "Disk$($i)Capacity(MB)" -Value ($_.CapacityGB*1024) -MemberType NoteProperty    $row | Add-Member -Name "Disk$($i)Controller" -Value ($_ | Get-ScsiController).Name -MemberType NoteProperty    $row | Add-Member -Name "Disk$($i)Datastore" -Value $_.FileName.Split(']')[0].TrimStart('[') -MemberType NoteProperty    $i++  }  while($i -le 8){    $row | Add-Member -Name "Disk #$($i) Name" -Value $null -MemberType NoteProperty    $row | Add-Member -Name "Disk #$($i)" -Value $null -MemberType NoteProperty    $row | Add-Member -Name "Disk$($i)path" -Value $null -MemberType NoteProperty    $row | Add-Member -Name "Disk$($i)Capacity(MB)" -Value $null -MemberType NoteProperty    $row | Add-Member -Name "Disk$($i)Controller" -Value $null -MemberType NoteProperty    $row | Add-Member -Name "Disk$($i)Datastore" -Value $null -MemberType NoteProperty    $i++  }  $report += $row}
  
  $report  | Export-Csv -path virtual_disks2.csv -notype
  

• Best practices for large virtual disk

  I would add a large virtual disk (16 TB) to use as a backup storage and ideally thin to allow potential available use of, at least initially, a lot of free space.  Headache is the limit of 2 TB for virtual disks in ESXi 5.

  I know that you can extend 2 TB virtual disks in the operating system (win 2008 r2, in this case).  But is it a good idea?  The underlying array is raid 6, so I guess it's safe, but it sounds at least potentially worriesome me on 8 discs.  Not a matter of concern?

  Performance?

  RDM is less flexible and might be impossible (matrix raid is local).

  Anyone have any suggestions on the best practices here?  What would you do?

  I do not recommend the use of the plan span for the file VMDK disks a bad 2 TB and its all parties (several ways that I saw - snapshot problems, corruption etc.)

  Because they are still local drives, you lose flexibility everything that I recommend using RDM.

  A huge ROW for this virtual machine.

  http://blog.davidwarburton.NET/2010/10/25/RDM-mapping-of-local-SATA-storage-for-ESXi/ This departure to configure it.

  As for what I would do, I've done this before and I used RDM, just for 8TB but still.

• Virtual disk on an iscsi SAN

  I have a question about virtual disks and how they actually read and wrote on the physical disks on a San.   Lets say I have the Exchange virtual server and a virtual SQL Server on the same RAID set on the SAN.  As you know, Exchange writes on the disc at random while MS SQL server writes sequentially.  Each app just write randomly and successively on their respective virtual disk?  If so, VMware wrote how physical disk with regard to how the application has written to the virtual disk?  For example, if Exchange writes randomly on the disc, which is technically the virtual disk on the ESX host file, VMware writes the changes to virtual disk random file on the physical disk?

  It depends on your performance needs - usually it's a good practice (virtualized or not) in order to isolate the workloads that shouldn't be able to influence the other.

  So, you can choose to create small groups of raid for the individual applications.  This has the advantage of better insulation, but at the cost of reduced performance for this application (and reduced the efficiency of storage capacity).

  It depends on your business needs.  If your SQL server server have been got nutso and eats all your IOPS / s, it would be OK that the Exchange has become terribly slow until you figured it out?  If so, then of course keep 1 large group.  If this isn't the case, then it split and bite the bullet on the cost.

• thin virtual disk have full size allocated - seems

  I have created a virtual machine with the thin disc type, give it a capacity of 500 GB, install the operating system and its actuall size is 3.60 GB I can check of Vsphere, the disc name is "vmname.vmdk".

  now I want it moved to another server esxi, but when I started downloding, its size became very larg and reached same 171 GB of the drive was renamed "vmname - flat hard"(sur où j'étais le téléchargement) and ends my disk space on the local computer where I was downloading, how I can upload and download with the same size means 3.60 GB "» ,

  Please guide me

  Welcome to the community,

  provisioning is a feature of VMFS file system, this is why the virtual disk inflates its provisioned size when uploading it. What you could do is to export the virtual machine (file-> export) as an OVF and import it on the destination host.

  André

• Specify the size of the virtual disk beyond 256 GB

  I'm editing the seetings on a virtual machine to have another drive.

  When I create a disk I select the size of the drive, 1 TB. I point to the location of LUN 30 data store (2 TB).

  When I click Next, I get the following message:

  The capacity of the disk is entered was not properly formed number or was out of reach. It has been replaced by the nearest acceptable value.

  This means - there is a procurement policy that I can change or what I need to select a card raw SAN LUNS?

  The maximum size of virtual disk on a store of data before ESXi 5 depended on the size of the selected block when the data store has been created/formatted. Please take a look at the tables to http://kb.vmware.com/kb/1012384 to see the file sizes maximum depending on the block size of the data store.

  André

• persistent disk capacity has not increased

  Hello

  My quality of view office is almost at its maximum capacity, I wish to bring to 2 GB.

  I tried to change the size of the disc continued its pool to 20480 MB but no change. Office as persistent disc view is still 2 GB. I need to change my virtual disk of individual desktop view instance (linked clone) for persistent 20 GB disk and extend it with diskpart?

  Yes, the change will not take place on new desktop computers that are created.  For an existing desktop computer, you will need to update the persistent drive by modifying the virtual machine settings, increasing and then something using the to expand inside the BONE.