Formula to determine the size of the data store

Similar Questions

• error message about the size of the data store

  I installed ESXi 5.1.0 on VMware workstation and interfaced the vsphere client management interface. It's all about

  Windows 7 laptop. I am now installing a VMware vCenter Server device image by using the vsphere client. But I have

  get an error stating: the capacity of the drive specified is greater than the amount available on the data store. Click Cancel to

  back from the value of disk space? How is it determined? I tried to change the size of the data store

  but I still get the same error. I do it just with what I have at home, and I'm new to VMware technology.

  I found this KB: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003565

  And it seems to imply that the size of the block can be a problem. Block size for the data of my ESXi store is set to 1 MB, which is expected to support upward

  up to 256 GB. I can't imagine that I need more space.

  On a different note, would you please tell me how I can post a couple of groups? What is the policy on this?

  I took a glance at the file unit .ovf and given the size of the virtual disk that is required for the data disk rose from 60 GB to 100 GB with update 1.

  It can work to tweak/change the .ovf file, however, in this case I would simply create a larger store of data to meet the requirements for the virtual disks (25 + 100 GB + overhead).

  André

• 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. :-)

• Swapping hard drives for change/increase the size of the data store

  Hello:

  I have an ESXi host 4.1 with 2x146GB RAID1 array (datastore1), 4x300GB RAID5 array (datastore2).  I need more space so I intend to replace 2x146GB by 2x2TB.  I'll first move virtual machines from datastore1 to datastore2, then stop the machine, Exchange records and build the new table.

  • What I need to remove ESXi cfg datastore1. before you physically remove the drives, or will start ESXi gracefully and allow me to remove the data store?
  • I'll be able to add the new data store (2x2TB) to ESXi, ago, i.e. ESXi should see table once initialized on the machine?
  • Existing data warehouses have 1 MB block size max vmdk is 256GB.  I want the new data store to have the block size of 8MB so I can have more VMDK.  I think I can fix the block size of data store when it was created, are, i.e. the ESXi installation can have warehouses of data with different block sizes, are?

  
  

  Thanks a lot for the ideas you have!

  
  

  Bob

  1.) why not just delete the GUI data store before you remove the discs?

  2.) If your controller has the disks properly there should be no problem with their detection.

  3.) Yes, each data store may have a different block size. The block size can be selected when creating the data store on disk/LUN.

  André

• The data store size is smaller than the virtual disk

  Just deploy a new installation of ESXI 4.1 rev3 on a new Dell PE R520 server with 4 disks 1 GB configured in a single Bay RAID5.  When I connect with vSphere and go to Configuration > it shows storage data store being just 740 GB.  However when I go to storage adapters and select the vmhba it shows the complete 2.73 CT of the RAID array that I need to use.  Nowhere I chose Go 740 for the size of the data store, so I don't know how it has been brought to this size.  If I try to delete and re-create 740 GB is the maximum I can create.

  What I am doing wrong and how do I create a data store that uses all 2.73 CT?  Screenshots are attached.

  Thanks in advance,

  Ben

  4 ESXi does not support LUNS > 2 TB.  Any increase on a multiple of 2 TB, it's what you'll see (e.g. 2.73 TB - 2 TB =.73 to ~ = 740 GB you see).

  But the real question is why you install version 3 year of the hypervisor?

• No unit number available logic trying to increase the size of the data store

  I am trying to increase the size of my data store.

  When you look at the properties of the data store I can see that the current capacity is 738,29 GB and the local device has a capacity of 2.73 TB.

  (see image 1)

  However, when I click the button increase, there is no LUNS to select.  (this is the case even when you try to add a new data store).

  (see image 2)

  What I am doing wrong?

  

  

  I'm afraid that there is nothing that you can do without having to reconfigure the storage as long as you use vSphere 4.x. because of the overflow I mentioned earlier (see the KB article) ESXi is only able to use 2.73 TB modulo 2 TB-online ~0.73TB.

  Anything that you can do to use currently unused disk space is to reformat, either by dividing the current RAID volume (I guess it's a RAID!) in several logical volumes with less than 2 TB or reinstall the host - if taking in charge - with ESXi 5.x.

  André

• Property of block size of the data store

  How to get the block size defined in the configuration of the data store tab. Is there a property, I should be looking. Currently, I tried getting the object managed data store but were not able to get the size of the block that.

  If you are looking for the solution with PowerCLI, take a look at Re: version list VMFS and block size of all data stores

  André

• Gets the data store size

  Hello, I do not know if here is righ place to my question if not please tell me where I can post it.

  I am attemping the information on the data store size by CLI with order tracking.

  c:\Program Files (x 86) \VMware\VMware vSphere CLI\bin > vmkfstools.pl "C:\Prograare\VMware vSphere CLI\Perl\bin\perl.exe" - serve
  queryfs-/ vmfs/volumes/v7ksas17 - vihost jvelnx - vm01.tigre.in

  work of starts but he asks me user and password for the moment that I run.

  I want to move this authentication directly by the CLI only after "ENTER".

  Is it possible? How?

  Thank you

  If you use the vCLI under Windows, you can use the passthroughauth - assuming you connect in Windows system with the same credentials that you would login to your vSphere environment.

  If this isn't the case, you can also specify the user name and password by specifying it only on the same command:

  for example

  vmkfstools.pl - Server [VC] - queryfs/vmfs/volumes/v7ksas17 - vihost jvelnx - vm01.tigre.in - username [USER] - password [COL]

  Also, you can create a session file and then specify that, in this way, you don't need to have your credentials in clear text.

  You can take a look at the additional documentation by auth options here - http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vcli.getstart.doc_50%2Fcli_run_remote.5.3.html

• VMX file larger than the maximum size supported by the data store

  Hi all

  I seem to be getting a strange error trying to a virtual machine that is located on a snapshot VMFS5, to the data store format.

  The virtual machine (VMDK and VMX file) is installed on a thin provisioned 2 TB datastore which has the value VMFS5 formatting.  It is a data store new with no other VM on it.  I had problems in the past with the datastore block sizes (1 MB, 2 MB, 4 MB, 8 MB on VMFS3), however, I thought that VMFS5 got rid of the question, since it's all blocks of 1 MB and all files in the virtual computer are on the same data store.

  The error I get indicates that the VMX file is too large for the data store (used Im saying "unspecified file), however, if I do the independent 2 TB disk snapshots through the fine.  The virtual machine has two virtual disks, a 50 VMDK of GB and a thin 2 TB VMDK (200 GB used).  I tried fast vMotioning the VMDK and VMX to other data formatted VMFS5 stores and still get the same error.

  I'd appreciate any help and ideas.

  Thank you

  Travis

  Although the block size limit is party, maximum 2 TB file size less 512octets still exists. Since a Flash disk can grow waist put in service the basic disk more overhead for the metadata, the maximum size of virtual disk - to be able to create snapshots - is 2032 GB.

  See "calculation time system required by the snapshot files" at http://kb.vmware.com/kb/1012384

  André

• Error: snapshot file < uspecified filename > is greater than th emaximum size supported by the data store

  I get the following error.

  File & lt; uspecified filename & gt; is superior to th emaximum supported by the data store

  My vm is 1024 GB, my block size is 4 MB and I 5.05 TB of free space.  The navigation data store, I see that there is a snapshot file incomplete 2gigs in size. I made snapshots to create in a different location from http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1002929 but still the same problem. Thanks for any help

  The virtual disk is too large to create a snapshot on a 4MB block size data store. The maximum size of VMDK is 1,016 Go.

  See "calculation time system required by the snapshot files" in http://kb.vmware.com/kb/1012384

  André

• Block size is too small - reformat the data store or create files VMDk 2?

  Hello

  I'm new to VMware and so far I absolutely love everything about her!  Well, I was not too happy when I realized that I can't create more than 256 GB a drive without reformatting the VMFS datastore.   Apparently, I accepted the block size of 1 MB by default during the installation...   I now need to configure a file server with about 500 GB of storage.  The data store with a larger block size (4 MB would be fine for me) reformatting is easy enough?  I am currently working on the first host ESXi 4.1 and will move to set up 2 more hosts in the coming weeks.  I read somewhere on the forum that ESXi 4.0 doesn't let you change the block size by default of 1 MB - is this true or relevant to 4.1?

  Currently, I have only 2 small VMs on that host, and these can be easily saved and put offline for a few hours, if necessary.  When starting the server, I created a single RAID array that holds ESXi and all virtual machines - does that mean that I have to reinstall ESXi in order to increase the size of the block?

  An alternative that I can get to is to simply create 2 255 GB VMDK each and load distribution of storage in the guest operating system (Win 2008).   Performance wise, is a disc more great and better (or worse) than the two smaller disks?

  On a related note, what should I choose for the "Independent" option when you add a new virtual disk?  Default is disabled (not independent).

  Your thoughts, focus and expertise are welcome and will be greatly appreciated!

  Thanks in advance,

  Dothan

  Dothan,

  You should power (after the virtual machine backup) remove the current data store and create a new one with the new block size. I did not have this on ESXi 4.1 again, however, he worked on ESXi 4.0.

  The maximum size of VMDK. If you want ot be able to take pictures, make sure you subtract twice the size of block in GB of the documented maximum size.

  Block size 1 MB--> 254 GB (= 256 GB, 2 GB)

  Block size of 2 MB--> 508 GB (= 512 GB - 4 GB)

  Size of block 4 MB--> GB 1 016 (= 1 024 GB - 8 GB)

  Block size of 8 MB--> GB 2 032 (= 2 048 GB to 16 GB)

  André

  EDIT: Just the KB for the maximum sizes. http://KB.VMware.com/kb/1012384

• File is greater than the maximum size supported by the data store "Datastore1".

  Okay, I'm trying to create a virtual machine from 350 GB.  I need to run a database of 283 GB to test / Proof of concept that will grow more than 325 GB. I get this error message

  -

  ---

  Error

  -

  ---

  File is larger than the maximum size supported by datastore 'Datastore '.  vm name.domain.com/server name.domain.com.vmdk

  -

  ---

  Ok

  -

  ---

  I have read that I need to increase the size of the block, but I need to remove the data store. Is it the same on ESXi 4.0?  I have 4 other VM about 150 GB. Please tell me I'm wrong.  Please...

  Same rules apply.  Create an another LUN with the correct block size and away files or hang the lun and recreate

  Steve Beaver

  VMware communities user moderator

  VMware vExpert 2009

  ====

  Co-author of "VMware ESX Essentials in the data center" virtual

  (ISBN:1420070274) Auerbach

  Come and see my blog: www.theVirtualBlackHole.com

  Come follow me on twitter http://www.twitter.com/sbeaver

  *Virtualization is a journey, not a project. *

• The data store size decreases!

  HII alll,

  I have a virtual machine running windows server 2003, with 135 GB hdd, I noticed in the data of this vm store two files from virtual drive...

  the first vmname.vmdk with size 135 GB and the other is vmname - 00001.vmdk with 15 GB and gettting increase day after day, until it reached today 18 GB

  the free space of data store becomes a decrease coz the vmname - 00001.vmdk file... I don't know what is it? and how can I solve this problem.

  It worsen now coz if there is no space in the data store the virtual machine will be down...

  any idea please?

  It's a snapshot.  Right click on the VM and go in your snapshot Manager you will probably see it there.

• How to extend the size of the data store

  Hello
  
  Everyone knows how to perform this task?
  
  
  Thank you
  
  
  
  Lewis

  As long as you have enough memory and disk space to accommodate the largest data store, the procedure is as follows:

  1. stop the data store and make sure that it is unloaded from memory

  2. increase the values for PermSize or TempSize on the DSN (sys.odbc.ini) parameters

  3. load the store data in memory again.

  Fact!

  If you use TimesTen 11 g, step (3) must be performed as long as the user administrator of the o/s instance.

  Chris

• Free space in the data store is lower we shouldn't

  Hello

  I'm under VMware ESXi on HP Proliant DL380 G5 server - the data store has a global capacity of 678 GB, with now 34 GB free. I have 5 VMs running:

  reader1/lecteur2

  (1) Win2k3: 50 / 100

  (3) Win2k3: 50 / 50

  (1) Windows XP: 10

  Oh - and the two models, one for the server (50) and a XP (10)

  Yesterday, I created a couple of clones of the XP, 1 with Vmkfstools - i and the other with vConverter - especially for the practice, but they are only 10 GB. Before my creations, free space read about 115 GB - then she got at the moment, I noticed 34GB. I deleted the two new virtual machines thinking I came home back from space, but no dice. Math is not my best subject, but this does not seem to add up. Do something wrong, I missed something?

  Is it possible to reclaim that space? Before I thought to check with you guys, it dawned on me that I could stop all VMs and restart the host, but if there is another way, I want to know it.

  Linda

  Browse the data store - go to the "Home" view - inventory - data warehouses, click a data store, and then select Browse.

  Look in the subdirectory for each virtual computer and determine that seem abnormal large size files and total size of all files that exceed the size of the virtual disks assigned to the virtual machine.  If you specify then what are the names of the files a plan for how to get rid of them.