Property of block 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é

• the maximum size of the data store in ESXi 4

  as I don't have a lot of space left on my data vmfs3 store, plans to add a 3 TB of HDD to the ESXi 4.1 Host. I will then use the new HDD for a creation of a new data store.

  I also want to ensure that the block size is the same as the existing data store.

  Please notify.

  Thank you.

  The maximum size of the LUN/disk in this case is 2 TB less 512 bytes (see KB VMware: ESX/ESXi 3.x/4.x hosts don't support 2 TB LUN for more details). The maximum size of virtual disk with a block size of 4 MB, please take a look at the article I mentioned in my previous post.

  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é

• 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é

• Formula to determine the size of the data store

  Is there a formula or a rule of thumb used to determine the size of a data store?

  For example, if I have 10 virtual computers that will need 20 GB of disk space, how big the data store be? I know that I have 200 GB of space for real virtual machines, but what other factors should be considered when sizing the data store?

  We usually leave 15 to 20% free space on all our datastoes.

  Here is a good article that can be useful to you as well

  http://SearchVMware.TechTarget.com/Tip/0, 289483, sid179_gci1350469_mem1, 00.html

• 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

• Set the size of the data store

  It's been a while since I installed ESX from scratch, we rotated on 3.5 for over 3 years now, and we need to rebuild. I do not remember, but if I have a 1 TB LUN but I want two data stores that are 500 g each, I take that I can't have format ESX two separate LUN correct? I would need to go through my console for SAN and remove the 1 TB and create LUN 2 x 500 G.

  OK, you need to create a LUN with the VMFS data store.  Although it is possible to have several stores of data on a single LUN is certainly not recommended.

  If you have found this helpful at all prices please points using the correct or useful!  Thank you!

• Error e/s download large vmdk file to the data store

  Hi, I am looking to download a large file (400 GB) vmdk to our SAN by using the method of the vsphere client browser store data but get IO error when it gets to about 270 GB. Is there a limit to how big a file can be? any other recommended method?

  Thank you

  Rob

  What is the version of VMFS (VMFS3 or VMFS5) of the data store? In the case of VMFS3 there are limitations on file size depending on the block size of the data store (for example, 1 MB block size-> ~ 256 GB).

  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?

• ESXi 5.5 only 4 TB usable for the data store

  Hi all

  Although in vSphere Client 5,46 TB of capacity is visible, I can only use 3.64 TB to a data store.

  Configuration:

  -HP Proliant Microserver N40L

  -HP Smart Array P410/512 MB BBWC, FW 3.66 Controller

  -4 x 2 TB as a Raid5

  HP-ESXi - 5.5.0 - iso - 5.72 A

  I read a lot of articles on > limits of 2 TB of older versions of ESXi or controllers, limitation of 4 TB of c# vSphere Client, old firmware and esxi driver problems, etc.

  But I could not understand the problem.

  The P410 controller shows 5.5 TB:

  ~ # esxcli hpssacli cmd - q "controller connector = 1 see the config.

  Smart Array P410 in slot 1 (sn: PACCRID110510NR)

  Array A (SATA, used space: 0 MB)

  logicaldrive 1 (5.5 TB, RAID 5, OK)

  then 2I:0:5 (port 2I:box 0:bay 5, SATA, 2 TB, OK)

  then 2I:0:6 (port 2I:box 0:bay 6, SATA, 2 TB, OK)

  then 2I:0:7 (port 2I:box 0:bay 7, SATA, 2 TB, OK)

  then 2I:0:8 (port 2I:box 0:bay 8, SATA, 2 TB, OK)

  MS (Vendor ID PMCSIERA, model SRC 8x6G) 250 (WWID: 5001438013D9F37F)

  ESXi obviously knows the same size:

  ~ # Esxcli storage core devices list

  NAA.600508b1001ca5e68adc0bc4bc508d6e

  Full name: Serial Attached SCSI disk HP (naa.600508b1001ca5e68adc0bc4bc508d6e)

  Definable display name: true

     Size: 5723091

  Device type: Direct access

  Multichannel plugin: NMP

  Devfs Path: /vmfs/devices/disks/naa.600508b1001ca5e68adc0bc4bc508d6e

  Vendor: HP

  Model: VOLUME LOGIC

  Review: 3.66

  SCSI level: 5

  (etc.)

  But does that 4 TB:

  ~ # df h

  Size of filesystem used available use % mounted on

  VMFS-5 T 3.6 2.1 T 1. 5 t 58% / vmfs/volumes/mainstorage

  vfat 249.7 M 177.2 M 72.6 M 71% / vmfs/volumes/aeda2aeb-c934ad60-46ce-cb77abdfabaa

  vfat 249.7 M 175.9 M 73.9 M 70% / vmfs/volumes/c8ace7e9-a96a5914-16 d 4-a697ad4634d9

  vfat 285.8 M 191.4 M 94.4 M 67% / vmfs/volumes/55d7af6e-a25f7c97-c3ec-6805ca0de93c

  I tried to increase the size of the data store, last used area was 11720890367 and last sector was 11720890510 which doesn't really seem to translate into an increase of 1.8 to.

  Thanks for your help.

  DC

  Your output, it shows that there are two partitions vmfs

  3 10229760 3907029134 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

  4 3907031040 11720890367 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

  A partition with 1.8 to and another with 3.8 to.   That's the reason why you see only 3.8 to

  I don't know why the 1.8 to vmfs volume is not list anywhere (which does not appear in the list of file system of storage of esxcli also). Do you have any before partition created manually. If you think that if there is no data in this 1.8 to vmfs partition you can remove it by using the partedutil command and then use this free space to extend the existing 3.8 to. But do not forget before you delete the partitiaon

• install esxi 4.1 and the data store on the same server

  Hello

  I want to install esxi 4.1 and the data store on the same server.

  My problem is that I can't make partitions to really separate them and I would reinstall esxi without wiping the data store.

  Y at - it another way to put a record out of the raid only to install esxi.

  I also do not install on a USB key.

  Thank you

  AZEL says:

  Hello

  I want to install esxi 4.1 and the data store on the same server.

  My problem is that I can't make partitions to really separate them and I would reinstall esxi without wiping the data store.

  Y at - it another way to put a record out of the raid only to install esxi.

  I also do not install on a USB key.

  Thank you

  AZEL,

  Can you give us more details about your current environment?  What is the size and the data store space used? Do you have any storage of additional network attached to the host (for backup purposes)?

  My assumptions of your post do you have 1 stand-alone host with ESXi 4.1 aready installed and you also have a local data store on the same host, but you want to re - install ESXi 4.1 while keeping the contents fo the data store.  Is this correct?

• 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

• 0 blocks free PTR - cannot create new files on the data store

  We have been experiencing problems trying to power on virtual machines. When attempting to power on virtual machines, we see the error "cannot extend the pagefile from 0 KB to 2097152 KB".

  We checked the .vswp file are created in the folder of the Virtual Machine on the data store. Connection to the ESXi host, we have seen the following in vmkernel.log error message:

  (2016 01-16 T 21: 19:40.556Z cpu1:4971732) WARNING: Res3: 6984: "freenas-6-ds": [rt 3] No. Space - has not found enough resources after the second pass! (requis_:_1,_trouvé_:_0) 2016-01 - 16 T 21: 19:40.556Z cpu1:4971732) Res3: 6985: "freenas-6-ds": [rt 3] resources t 0, e 0, PN 16, BM 0, b 0, RCs u 0, i 0, 4031 nf, pe 0, 0 2016-01-16 T 21 oe: 19:40.556Z cpu1:4971732) WARNING: SwapExtend: 683: impossible to extend the pagefile from 0 KB to 2097152 KB.

  This was surprising given that we have about 14 TB of space available on the data store:

  [root@clueless:~] df h

  Size of filesystem used available use % mounted on

  VMFS-5 20.0 T 5.4 T 14.6 T/vmfs/volumes/freenas-six-ds 27%

  However, when we use "dd" to write a 20 GB file, we would get "no space left on device:

  [root@clueless:/vmfs/volumes/55a00d31-3dc0f02c-9803-025056000040/deleteme] dd if = / dev/urandom of = deleteme bs = 1024 count = 2024000

  DD: writing "deleteme": no space is available on the device

  263734 + 0 records in

  out 263733 + 0 reviews

  [root@clueless:/vmfs/volumes/55a00d31-3dc0f02c-9803-025056000040/deleteme] ls - lh deleteme

  -rw - r - r - 1 root root 19 Jan 255,1 M 01:02 deleteme

  We checked that we have free inodes:

  The ramdisk name system include in reserved Coredumps used Maximum reserved free use pic free maximum allocated Inodes used Inodes Inodes Mount Point

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

  root of true true 32768 KiB 32768 KiB KiB KiB 99% 99% 9472 4096 3575 176 176.

  true true etc 28672 KiB 28672 KiB 284 KiB 320 KiB 99% 99% 4096 1024 516/etc

  Choose true true 0 KiB KiB 0 KiB KiB 0 100% 0% 8 1024 8192 32768 / opt

  var true true 5120 KiB 49152 484 516 99% 90% 8192 384 379 KiB KiB KiB / var

  tmp false false 2048 KiB 262144 KiB 20 KiB 360 KiB 99% 99% 8 256 8192/tmp

  false false hostdstats KiB 310272 KiB 3076 KiB 3076 KiB 99 0% 0% 8192 32 5/var/lib/vmware/hostd/stats

  
  

  We believe that our cause is due to have 0 free blocks of PTR:

  [root@clueless:/vmfs/volumes/55a00d31-3dc0f02c-9803-025056000040] vmkfstools Pei - v 10/vmfs/volumes/freenas-six-ds.

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

  File system label (if applicable): freenas-six-ds

  Mode: public TTY only

  Capacity 21989964120064 (blocks of files 20971264 * 1048576), 16008529051648 (15266923 blocks) prevail, max supported size of the 69201586814976 file

  Volume creation time: Fri Jul 10 18:21:37 2015

  Files (max / free): 130000/119680

  Blocks of PTR (max / free): 64512/0

  Void / blocks (max / free): 32000/28323

  The secondary blocks of Ptr (max / free): 256/256

  Drop blocks (approve/used/approve %): 0/5704341/0

  Blocks of PTR (approve/used/approve %): 64512/0/0

  Void / blocks (approve/used/approve %): 3677/0/0

  Size of volume metadata: 911048704

  UUID: 55a00d31-3dc0f02c-9803-025056000040

  Logical unit: 55a00d30-985bb532-BOI.30-025056000040

  Partitions split (on 'lvm'):

  NAA.6589cfc0000006f3a584e7c8e67a8ddd:1

  Instant native is Capable: YES

  OBJLIB-LIB: ObjLib cleaned.

  WORKER: asyncOps = 0 maxActiveOps = 0 maxPending = 0 maxCompleted = 0

  When we turn off a virtual machine, it will release 1 block of PTR and we would be able to on another VM / create the 20 GB file using "dd". Once we reached 0 free blocks of PTR, we are unable to create new files.

  Can anyone give any suggestions on how we may be able to clear the blocks PTR? We have already tried to restart all services of management on all ESXi hosts connected.

  FreeNAS is not running on a virtual machine.

  We solved the problem by finding a lot PTR blocks have been used by many of our models of virtual machine. Remove the disk models solved the problem.