{"id":597,"date":"2021-09-20T12:25:25","date_gmt":"2021-09-20T12:25:25","guid":{"rendered":"https:\/\/robinplomp.com\/?p=597"},"modified":"2022-01-12T14:02:08","modified_gmt":"2022-01-12T14:02:08","slug":"file-locks-on-vsphere","status":"publish","type":"post","link":"https:\/\/robinplomp.com\/?p=597","title":{"rendered":"File locks on vSphere"},"content":{"rendered":"

\"vmware_vSphere7_graphic_thumb\"<\/a>In a project we where starting an action to export a VM to an OVF file. We launched the export from the vSphere WebClient. During the export action the file stream failed and we cancelled the export action. Because we where running into a time restriction with the allowed time frame we wanted to boot the machine so it would be available to the end users.
\n
\nOnce we booted the machine we received the following error: File system specific implementation of Ioctl[file] failed. <\/em>This resulted in not being able to boot the machine.<\/p>\n

Together with VMware Support we where able to resolve this issue by identifying what was locking this VM files, and remove the lock.<\/p>\n

\"2021-09-20<\/a><\/p>\n

With the command lsof | grep vm name <\/em><\/strong>we get a list of the current locks on the files for this VM. In the above screenshot you can see that the vpxa process is still locking the files. The process that is locking the VM files (vpxa) is the vCenter Agent Services.<\/p>\n

With the kill \u20139 67866
\n<\/em><\/strong>The \u20139<\/em><\/strong>  switch means, the process will be killed by the kernel. This command cannot be ignored by the OS.<\/p>\n

After the kill command we run the lsof command to be sure that the process is gone. We are now able to boot the machine.<\/p>\n","protected":false},"excerpt":{"rendered":"

In a project we where starting an action to export a VM to an OVF file. We launched the export from the vSphere WebClient. During the export action the file stream failed and we cancelled the export action. Because we where running into a time restriction with the allowed time frame we wanted to boot … Lees verder File locks on vSphere<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[33,22],"tags":[44],"class_list":["post-597","post","type-post","status-publish","format-standard","hentry","category-vcenter","category-vmware","tag-file-locks"],"_links":{"self":[{"href":"https:\/\/robinplomp.com\/index.php?rest_route=\/wp\/v2\/posts\/597","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/robinplomp.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/robinplomp.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/robinplomp.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/robinplomp.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=597"}],"version-history":[{"count":2,"href":"https:\/\/robinplomp.com\/index.php?rest_route=\/wp\/v2\/posts\/597\/revisions"}],"predecessor-version":[{"id":712,"href":"https:\/\/robinplomp.com\/index.php?rest_route=\/wp\/v2\/posts\/597\/revisions\/712"}],"wp:attachment":[{"href":"https:\/\/robinplomp.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=597"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/robinplomp.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=597"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/robinplomp.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=597"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}