- 论坛徽章:
- 13
|
这位朋友，我正好使用i5版本，我虽没有遇到此问题。下面的文章对你有用
ESX/ESXi 3.x/4.x hosts do not support 2-terabyte LUNs
Details
If you present a 2-terabyte (TB) or larger LUN to one or more ESX/ESXi hosts, you may experience these symptoms:
•You are unable to create a datastore on the LUN
•The ESX/ESXi host does not assign a block device to the LUN
•VMkernel log messages may indicate that the ESX/ESXi host cannot read the capacity of the LUN
•The ESX/ESXi host does not report the correct size on an RDM larger than 2TB
•VirtualCenter or vCenter Server reports incorrect size for the LUN
•When attempting to vMotion a virtual machine using an RDM 2TB or larger from an ESX/ESXi 3.5 to an ESX/ESXi 4.0 host fails. These error messages are found in the vmware.log of the virtual machine:
vmx| Msg_Post: Error vmx| [msg.scsi.esx.diskTooBig] Disks bigger than 2TB - 512B are not supported. vmx| [msg.scsi.esx.virtualDevFailed] Unable to create virtual SCSI device for scsi#:#, '/vmfs/volumes/<datastore>/<vm>/<disk>.vmdk' vmx| [msg.moduletable.powerOnFailed] Module DevicePowerOn power on failed.
•In the VMKernel Logs of the ESX Host you see one or more lines similar to this:
vmkernel: 0:00:41:40.802 cpu1:4177)WARNING: ScsiDeviceIO: 1462: Device 'naa.6001e4f0107c3600110a158c807e60bf': Capacity (numBlocks=0x105e40000) exceeds maximum supported device size of 2TB - 512 Bytes
Note: A cold migration to an ESX 4.0 host followed by a power on attempt has a similar result.
•In vCenter Server 4.0 or later, you see this error:
Error during the configuration of the host: Failed to update disk partition information.
•In the hostd.log file, you see entries similar to:
[F57E1B90 verbose 'HostsvcPlugin' opID=3E815AF8-00000080-6e] Failed to get disk partition information for /vmfs/devices/disks/naa.6001e4f0107c3600110a158c807e60bf
[F5AF5B90 warning 'Partitionsvc' opID=3E815AF8-00000081-d1] Unable to get partition information for /vmfs/devices/disks/naa.6001e4f0107c3600110a158c807e60bf
[F5AF5B90 warning 'Partitionsvc' opID=3E815AF8-00000081-d1] Status : 255
Output:
Error : A bug has been detected in GNU Parted. Refer to the web site of parted http://www.gnu.org/software/parted/parted.html for more informations of what could be useful for bug submitting! Please email a bug report to bug-parted@gnu.org containing at least the version (1.8.1) and the following message: Unable to determine the size of /vmfs/devices/disks/6001e4f0107c3600110a158c807e60bf (Numerical result out of range). Unable to get device /vmfs/devices/disks/6001e4f0107c3600110a158c807e60bf
Solution
Note: As of ESXi 5.0, support for LUNs larger then 2TB is available with both VMFS5 datastores and Physical-mode RDMs. However, virtual disks used in virtual machines and Virtual-mode RDMs are still limited to 2TB - 512 bytes. For more information, see vSphere 5 FAQ: VMFS-5 (2003813).
Cause
The largest LUN size which can be presented to an ESX/ESXi host is 2TB - 512 bytes. This limitation is outlined in the Configuration Maximums guide for the appropriate version of ESX/ESXi.
Understanding the Limitation
VMware ESX and ESXi uses the SCSI-2 standard. As per the SCSI-2 standard, ESX uses a READ_CAPACITY (10-byte) call which returns a 32-bit number to represent the size of the LUN.
Although the call is capable of returning a 32-bit number, only the 0x00000000 to 0xfffffffe values can be used. The value 0xffffffff is reserved.
Based on the standard, the largest valid LUN capacity support is (2^32)-1 sectors. This is the math involved in the calculation:
(2^32) = 4294967296
4294967296 - 1 = 4294967295
If we take the above number and multiply it by 512 bytes per sector we get the size limitation in bytes:
4294967295 x 512 = 2199023255040
The limit of 2TB translates to:
•4294967295 sectors
•2199023255040 bytes
Raw Device Mapping Limit
In the case of physical mode RDMs, the SCSI traffic sent by the guest operating system to do reads or writes is passed through by the VMware ESX storage layer to the underlying storage. This allows some guests to break the 2-terabyte limit, but this is an unsupported configuration because the storage stack of the ESX is not designed to handle such capacity.
Note: When migrating and powering on virtual machines, ESX/ESXi 4.0 enforces the 2TB - 512 bytes limit. ESX 3.5 does not enforce this limit.
Workaround
Although the LUN size is limited to 2TB - 512 bytes, the VMFS and datastore volume size limit is much greater. The maximum volume size is 64TB - 16KB. This can be accomplished by leveraging the maximum extents (32) per volume.
If you require a single datastore that is larger than 2TB - 512 bytes in size, you may want to add extents so that the datastore resides on multiple LUNs of 2 TB - 512 bytes or less.
For information on extents, see the ESX Configuration Guide.
Considerations
Keep these considerations in mind when implementing the workaround:
•Once you add an extent to a datastore, you cannot remove the extent.
•The maximum file size which can reside on a datastore is based on the block size of the filesystem. The maximum block size for VMFS version 3 (used by ESX3 and ESX4) is 8MB, which limits the maximum file size to 2TB - 512 bytes in size. For more information about the maximum file size, see the Configuration Maximums for the appropriate version of ESX.
If you install ESX 3.5 Update 4 on a host that has a local disk larger than 2TB, you may have trouble booting. For more information, see Mounting root fails after installing ESX 3.5 when local storage exceeds the 2 terabyte limit (1012757).
|
|
免费注册
发表于 2012-03-27 19:01
assthrough RDMs are supported up to ~60TB in size. 
