vSAN reporting Device or resource busy for vswp files
Article ID: 318502
Updated On:
Products
VMware Cloud Foundation
VMware vSAN
Issue/Introduction
Symptoms:
Note: Dates, times, names, and IDs will vary depending on your environment
2020-09-24T20:35:26.329Z warning hostd[2501352] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/9ec34e5f-129b-eb07-ce59-ecf4bbcf0454/Ubuntu 20.04 - JUMP Dallas.vmx opID=7f26ddf8-f0-9df8 user=vpxuser:VSPHERE.LOCAL\Administrator] Failed to get object size, '/vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/9ec34e5f-129b-eb07-ce59-ecf4bbcf0454/vmx-Ubuntu 20.04 - JUMP Dallas-2648678417-1.vswp': Device or resource busy
2020-09-24T20:35:26.329Z info hostd[2501352] [Originator@6876 sub=Libs opID=7f26ddf8-f0-9df8 user=vpxuser:VSPHERE.LOCAL\Administrator] OBJDESC-LIB : Unable to the read the descriptor file '/vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/9ec34e5f-129b-eb07-ce59-ecf4bbcf0454/vmx-Ubuntu 20.04 - JUMP Dallas-2648678417-1.vswp' (Device or resource busy)
2020-09-24T20:35:26.329Z warning hostd[2501352] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/9ec34e5f-129b-eb07-ce59-ecf4bbcf0454/Ubuntu 20.04 - JUMP Dallas.vmx opID=7f26ddf8-f0-9df8 user=vpxuser:VSPHERE.LOCAL\Administrator] File - failed to get objectId, '/vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/9ec34e5f-129b-eb07-ce59-ecf4bbcf0454/vmx-Ubuntu 20.04 - JUMP Dallas-2648678417-1.vswp': Device or resource busy (1048580)
2020-09-24T20:35:26.365Z info hostd[2101455] [Originator@6876 sub=Libs opID=17e7fb5a-f2-9dfb user=vpxuser:VSPHERE.LOCAL\Administrator] OBJDESC-LIB : Unable to read descriptor : /vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/5d18255f-6353-6ca3-f265-246e964e71c4/vmx-2111 - MBG 11.0.0.294 - 2-3162313272-1.vswp (Device or resource busy).
2020-09-24T20:35:26.365Z warning hostd[2101455] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/5d18255f-6353-6ca3-f265-246e964e71c4/2111 - MBG 11.0.0.294 - 2.vmx opID=17e7fb5a-f2-9dfb user=vpxuser:VSPHERE.LOCAL\Administrator] Failed to get object size, '/vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/5d18255f-6353-6ca3-f265-246e964e71c4/vmx-2111 - MBG 11.0.0.294 - 2-3162313272-1.vswp': Device or resource busy
- vSAN reporting Device or resource busy (1048580) for vswp files
- The VMs may fail to migrate to another ESXi host.
- The VM snapshot consolidation will fail.
- The message "File - failed to get objectId, ..... Device or resource busy (1048580)" is seen in the hostd log, sometimes flooding the log.
- Example log messages:
Note: Dates, times, names, and IDs will vary depending on your environment
2020-09-24T20:35:26.329Z warning hostd[2501352] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/9ec34e5f-129b-eb07-ce59-ecf4bbcf0454/Ubuntu 20.04 - JUMP Dallas.vmx opID=7f26ddf8-f0-9df8 user=vpxuser:VSPHERE.LOCAL\Administrator] Failed to get object size, '/vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/9ec34e5f-129b-eb07-ce59-ecf4bbcf0454/vmx-Ubuntu 20.04 - JUMP Dallas-2648678417-1.vswp': Device or resource busy
2020-09-24T20:35:26.329Z info hostd[2501352] [Originator@6876 sub=Libs opID=7f26ddf8-f0-9df8 user=vpxuser:VSPHERE.LOCAL\Administrator] OBJDESC-LIB : Unable to the read the descriptor file '/vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/9ec34e5f-129b-eb07-ce59-ecf4bbcf0454/vmx-Ubuntu 20.04 - JUMP Dallas-2648678417-1.vswp' (Device or resource busy)
2020-09-24T20:35:26.329Z warning hostd[2501352] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/9ec34e5f-129b-eb07-ce59-ecf4bbcf0454/Ubuntu 20.04 - JUMP Dallas.vmx opID=7f26ddf8-f0-9df8 user=vpxuser:VSPHERE.LOCAL\Administrator] File - failed to get objectId, '/vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/9ec34e5f-129b-eb07-ce59-ecf4bbcf0454/vmx-Ubuntu 20.04 - JUMP Dallas-2648678417-1.vswp': Device or resource busy (1048580)
2020-09-24T20:35:26.365Z info hostd[2101455] [Originator@6876 sub=Libs opID=17e7fb5a-f2-9dfb user=vpxuser:VSPHERE.LOCAL\Administrator] OBJDESC-LIB : Unable to read descriptor : /vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/5d18255f-6353-6ca3-f265-246e964e71c4/vmx-2111 - MBG 11.0.0.294 - 2-3162313272-1.vswp (Device or resource busy).
2020-09-24T20:35:26.365Z warning hostd[2101455] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/5d18255f-6353-6ca3-f265-246e964e71c4/2111 - MBG 11.0.0.294 - 2.vmx opID=17e7fb5a-f2-9dfb user=vpxuser:VSPHERE.LOCAL\Administrator] Failed to get object size, '/vmfs/volumes/vsan:5230985995685575-d9778718df8c887f/5d18255f-6353-6ca3-f265-246e964e71c4/vmx-2111 - MBG 11.0.0.294 - 2-3162313272-1.vswp': Device or resource busy
Environment
VMware vSAN 7.0.x
VMware vSAN 6.7.x
VMware vSAN 6.7.x
Cause
The First Class Disk (FCD) process attempts to open the vswp binary vSAN object as a text descriptor file. This results in the warning message logged and in addition it slows down hostd and causes unnecessary IO messages to be sent to VMFS/VSAN storage.
Resolution
This issue is resolved in VMware vSphere ESXi 6.7 Patch ESXi670-202011002 and VMware vSphere ESXi 7.0 U1c. To download go to the Customer Connect Patch Downloads page.
Workaround:
There is no workaround for this issue. This needs hostd binary to change this behavior, which cannot be done safely without upgrade.
Workaround:
There is no workaround for this issue. This needs hostd binary to change this behavior, which cannot be done safely without upgrade.
Feedback
Yes
No
Powered by
