Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Re-signature operation of snapshot LUN is failing with fault: VmfsAlreadyMounted. (76989)

Last Updated: 2/27/2024Categories: Known IssueTotal Views: 12246Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Re-signature operation is failing with VmfsAlreadyMounted exception even though its original copy is not mounted/force mounted anywhere in the datacenter.

Mounting a snapshot LUN from vCenter UI fails with an error:

"VMFS volume with the same uuid is already mounted in the datacenter"

In vCenter vpxd. log reports following errors:

[VpxLRO] -- ERROR task-668821 -- datastoreSystem-80 -- vim.host.DatastoreSystem.resignatureUnresolvedVmfsVolume: vim.fault.VmfsAlreadyMounted:
--> (vim.host.UnresolvedVmfsResignatureSpec) {

-- ERROR task-668821 -- datastoreSystem-80 --
vim.host.DatastoreSystem.resignatureUnresolvedVmfsVolume: vim.fault.VmfsAlreadyMounted:
--> Result:
--> (vim.fault.VmfsAlreadyMounted) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    uuid = ""
-->    msg = ""
--> }
--> Args:
-->
--> Arg resolutionSpec:
--> (vim.host.) {
-->    extentDevicePath = (string) [
-->       "/vmfs/devices/disks/naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:1"
-->    ]

Re-signature via esxcli works fine from ESXi host.

Volume is not mounted on DR site or anywhere else as mentioned in KB: https://kb.vmware.com/s/article/2082643

Cause

The UnresolvedVmfsExtent returned by API QueryUnresolvedVmfsVolumes (from host side) is not filled with the vmfsUuid field. Issue occurs only if datacenter has at least one force mounted volume.

Impact / Risks

None.

Resolution

This issue is resolved in vCenter Server 6.5 Update 3f (build number 15259038) patch release. To download go to VMware Patch Download Center
This issue is resolved in vCenter Server 6.7 Update 3l (build number 17138064) patch release. To download go to VMware Patch Download Center

Workaround

Re-signature the snapshot volume from ESXi host directly using esxcli:

esxcli storage vmfs snapshot resignature -l label|-u uuid

For more details on mounting snapshot volumes, please see following KB and section:Command line:

vSphere handling of LUNs detected as snapshot LUNs

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
プリエンプティブ フェイルバックで、新しいスタンバイ T0 ルータの BGP ピアリングがアクティブのまま停止する (77023)

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

KB
•
vRealize Network Insight 5.1.0 クラスタのアップグレードが「Foundation DB のアップグレード...」で停止する (76958)

KB
•
vCenter Server 可能会报告错误的数据存储使用情况或可用空间。 (76880)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere

VMware vCenter Server Appliance

VMware vCenter Server

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

VMware vCenter Server 6.7.x

VMware vCenter Server 6.5.x

Take Our Survey

Support Assistant