Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Vixdisklib hangs when using SAN if the disk size in MB is not integer (66936)

Last Updated: 6/13/2019Categories: TroubleshootingTotal Views: 8581Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

When trying to use SAN transport mode to open the disk, it needs to fetch the mapped blocks. If the disk size in MB is not integer, the program can not get mapped bytes successfully. The length of mapped bytes is always 0 and blockmap fetch operation will not complete.

12452 27b4 02/20 HH:MM:SS 119226 YYYY-MM-DDT14:48:39.624+01:00 verbose -[10164] [Originator@6876 sub=Default] Fetching large block map: (4402339840 out of 1024 bytes mapped).
12452 27b4 02/20 HH:MM:SS 119226 YYYY-MM-DDT14:48:39.639+01:00 verbose -[10164] [Originator@6876 sub=Default] Fetching large block map: (4402339840 out of 1024 bytes mapped).

VDDK log always reports the same log and the number of mapped bytes never changes.

In VDDK log, it reports failure when writing to the end of the disk.

YYYY-MM-DD_HH:MM:SS.047 INFO  VDDK - 2019-04-10T05:20:52.046-04:00 error -[31430] [Originator@6876 sub=Default] San transport error: The specified request is invalid.
YYYY-MM-DD_HH:MM:SS.047 INFO  VDDK - DISKLIB-LIB   : RWv failed ioId: #2054 (318) (62) .
YYYY-MM-DD_HH:MM:SS.047 INFO  VDDK - VixDiskLib: Detected DiskLib error 318 (Unknown error).
YYYY-MM-DD_HH:MM:SS.047 INFO  VDDK - VixDiskLib: VixDiskLib_Write: Write 22 sectors to disk at 21176320 failed. Error 1 (Unknown error) (DiskLib error 318: Unknown error) at 6115.

In hostd.log, it reports Block range extends beyond the end of the underlying virtual disk.

YYYY-MM-DDTHH:MM:SS.170Z error hostd[1000081589] [Originator@6876 sub=Blklistsvc opID=b0e16a0-a3-bc0f user=vpxuser:VSPHERE.LOCAL\Administrator] Block range 10340 (1) extends beyond the end of the underlying virtual disk.

Cause

VDDK SAN transport mode is not supported with base VMDK size which is not multiple of 4K. This is due to a known SeSparse issue in querying for physical mappings when size is not 4K multiple. The block size is 1MB on a VMFS datastore in vSphere 5.0 and later releases. For example: such as 500.23 MB or 3250.739 MB

Resolution

To resolve this issue, increase the disk size in MB to integer.

Although we only find the issue when using SAN transport mode, we recommend customers to increase the disk size in MB to integer regardless of any transport mode. For Example: From 500.23 MB to 501 MB

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere Data Protection

VMware vSphere

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

VMware vSphere Data Protection 6.x

Take Our Survey

Support Assistant