知識庫

The ESX 4.x installer utilizes the default block size of 1MB when creating VMFS volumes. For additional information on the VMFS block size, see the Additional Information section, below.

The service console in ESX 4.x is stored in a VMDK file on a VMFS partition, typically located on local storage. While VMware ESX 4.x is running, you cannot reformat the volume with the intended block size. If you have already completed an installation of VMware ESX 4.x, are unable to reinstall the product with the intended block size using steps provided below, and you require a larger block size on the local VMFS partition, see Reformatting the local VMFS partition's block size in ESX 4.x (post-installation) (1013210).

New Installations: Formatting with a VMFS block size larger than 1MB

While the installer can be modified to format any new VMFS partitions with a specified block size, the following workarounds are also available:

• Re-install the ESX host on a different drive (for example, a second RAID set or boot from SAN), and leave the original disk for the VMFS volume. You can then choose your blocksize when creating the second datastore at a later time.
• Alternatively, install ESX 3.5, create the volume with desired blocksize or re-format the volume with the intended block size, then upgrade to ESX 4.x. Specify to use the existing VMFS volume to store your Console OS VMDK.
• Create a second RAID set, forming a discrete device or volume which can be utilized with the intended block size, post-installation.
• Carve out a new LUN, volume, on the local controller for a new volume. This, too can be utilized with the intended block size post-installation, but additional proecdures are required:
  
  Note: You cannot create a second datastore (via another partition) on the same drive via the ESX GUI. You must use the vmkfstools command. You may also need to create a partition on the free space first with the fdisk command:
  
  vmkfstools -C vmfs -b Xm -S local2mBS /vmfs/devices/disks/naa.xxxxxxxxxx:y 
  
  where: 
  
  
  • Xm is the blocksize (1m, 2m, 4m, or 8m).
  • local2mBS is your volume name. If the volume name has a space (for example, volume name ), enclose it in quotation marks (for example, " volume name").
  • naa is the naa identifier, and y is the partition number. To determine this, run ls -la in the/vmfs/devices/disks folder.
  • You can also specify the file system version in the command to execute correctly:
    
    vmkfstools -C vmfs3 -b Xm -S local2mBS /vmfs/devices/disks/naa.xxxxxxxxxx:y
    
    
  Note: Depending on your disk controller type, naa. may be replaced with eui., t10., or mpx.. For more information, seeIdentifying disks when working with VMware ESX (1014953).

Reconfiguring the ESX 4.x installer and formatting new VMFS volumes with a specific block size 

To reconfigure the installer to format VMFS partitions with a specified block size:

1. Boot the ESX installation DVD and choose Install in graphical mode.
2. Press Ctrl+Alt+F2 to switch to the shell.
3. Run this command:
   
ps | grep Xorg


4. Kill the PID which shows Xorg -br -logfile .... 
   
   Example: If this PID is 590, enter this command:
   
kill 590

Notes:
   
   • If you specified a GUI mode installation, killing the process identified as Xorg may switch you back to another console. If this occurs, press Ctrl+Alt+F2 to return to the previous console.
   • If after killing the Xorg process you see the message Press to reboot, press Ctrl+Alt+F3 to go to another console and continue working there without rebooting. 
     
     
5. Switch to the configuration directory. Enter this command:
   
   cd /usr/lib/vmware/weasel

   
6. Edit the configuration script. Enter this command:
   
   vi fsset.py
   
   Note: For more information on editing files, see Editing configuration files in VMware ESXi and ESX (1017022).
   
   
7. Locate class vmfs3FileSystem(FileSystemType).

8. Edit the blockSizeMB parameter to the block size that you want. It is currently be set to 1. The only values that work correctly are 1, 2, 4, and 8.
   
   Note: Press i for insert mode.
   
   
9. Save and close the file, press Esc, type :wq! and press Enter. The exclamation mark is needed to force the action of saving as the file is read-only.
   
10. Verify that the content has been changed. Enter this command:
    
    grep -i blockSizeMB fsset.py


11. Switch back to the root directory. Enter this command:
    
    cd /


12. Launch the installer with the new configuration. Enter this command:
    
    /bin/weasel
13. 

14. Based on VMware KB 1012683