OPERATIONAL DEFECT DATABASE
...
...
Cannot convert a Linux virtual machine using vCenter Converter Converting a Linux virtual machine times out and fails You see the error: umount: cannot umount /mnt/p2v-src-root/var: Device or resource busy In the VMware vCenter Converter logs, you see entries similar to:2012-03-13 18:47:26.568 'task-1' 4028627856 info Copying files from <IP>:/var to /mnt/p2v-src-root/var2012-03-13 18:47:26.569 'task-1' 4028627856 verbose LD_LIBRARY_PATH=/usr/lib/vmware-converter2012-03-13 18:47:26.569 'task-1' 4028627856 verbose PATH=/bin:/sbin:/usr/bin:/usr/sbin2012-03-13 18:47:26.569 'task-1' 4028627856 verbose Invoking /usr/lib/vmware-converter/copyFileSystem.sh with the following arguments:2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args[0]: --sshClient2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args[1]: /usr/lib/vmware-converter/ssh2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args[2]: --user2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args[3]: <username>2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args[4]: --host2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args[5]: <IP>2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args[6]: --port2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args[7]: 222012-03-13 18:47:26.569 'task-1' 4028627856 verbose args[8]: --sourceMountPoint2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args[9]: /var2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args\[10]: --targetMountPoint2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args\[11]: /mnt/p2v-src-root/var2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args\[12]: --sshConfigFile2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args\[13]: /usr/lib/vmware-converter/ssh.conf2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args\[14]: --sourceTarOption2012-03-13 18:47:26.569 'task-1' 4028627856 verbose args\[15]: --sparse2012-03-13 18:48:12.581 'Helper' 4037016464 verbose Converter Agent Helper ServiceInstance RetrieveContent2012-03-13 18:53:12.722 'Helper' 4062182288 verbose Converter Agent Helper ServiceInstance RetrieveContent2012-03-13 18:58:12.808 'Helper' 4078959504 verbose Converter Agent Helper ServiceInstance RetrieveContent2012-03-13 19:03:12.857 'Helper' 4053793680 verbose Converter Agent Helper ServiceInstance RetrieveContent2012-03-13 19:08:12.863 'Helper' 4078959504 verbose Converter Agent Helper ServiceInstance RetrieveContent2012-03-13 19:13:12.916 'Helper' 4099462848 verbose Converter Agent Helper ServiceInstance RetrieveContent2012-03-13 19:18:12.994 'Helper' 4045405072 verbose Converter Agent Helper ServiceInstance RetrieveContent2012-03-13 19:23:12.975 'Helper' 4090932112 verbose Converter Agent Helper ServiceInstance RetrieveContent2012-03-13 19:28:13.012 'Helper' 4037016464 verbose Converter Agent Helper ServiceInstance RetrieveContent2012-03-13 19:33:13.062 'Helper' 4078959504 verbose Converter Agent Helper ServiceInstance RetrieveContent2012-03-13 19:38:13.082 'Helper' 4062182288 verbose Converter Agent Helper ServiceInstance RetrieveContent2012-03-13 19:43:13.089 'Helper' 4090932112 verbose Converter Agent Helper ServiceInstance RetrieveContent2012-03-13 19:47:27.915 'task-1' 4028627856 error /usr/lib/vmware-converter/copyFileSystem.sh did not finish producing output after 3600 seconds2012-03-13 19:47:27.916 'task-1' 4028627856 info Exception caught during volume copying: /usr/lib/vmware-converter/copyFileSystem.sh did not finish producing output after 3600 seconds2012-03-13 19:47:27.916 'task-1' 4028627856 info Unmounting partition /dev/sdb72012-03-13 19:47:27.916 'task-1' 4028627856 verbose LD_LIBRARY_PATH=/usr/lib/vmware-converter2012-03-13 19:47:27.916 'task-1' 4028627856 verbose PATH=/bin:/sbin:/usr/bin:/usr/sbin2012-03-13 19:47:27.916 'task-1' 4028627856 verbose Invoking /bin/umount with the following arguments:2012-03-13 19:47:27.916 'task-1' 4028627856 verbose args[0]: /dev/sdb72012-03-13 19:47:29.930 'task-1' 4028627856 verbose Command return code: 1; result string: umount: cannot umount /mnt/p2v-src-root/var: Device or resource busy2012-03-13 19:47:29.930 'task-1' 4028627856 error '/bin/umount /dev/sdb7' failed. Return code: 1; message:umount: cannot umount /mnt/p2v-src-root/var: Device or resource busyNote: For information on log locations, see Collecting diagnostic information for VMware Converter (1010633)
This article identifies as issue on the operating system of the source Linux machine, that causes VMware vCenter Converter to fail. This affects all versions of VMware vCenter Converter that support hot-cloning of Linux operating systems.
This issue occurs if a file size reported within the operating system of the source Linux operating system is inaccurate. Specifically, In Red Hat Enterprise and Fedora version 4.x operating systems, this may be caused by the /var/log/lastlog file.. The /var/log/lastlog file is used to store information about successful logins to the operating systems. In earlier versions of Red Hat Enterprise Linux and Fedora 4.x, the file size can be misrepresented if this file is corrupted.
This issue is resolved in recent versions of Red Hat and Fedora. For more information and a patch to resolve this issue, contact Red Hat. To workaround this issue: Log in to the operating system as the root user. Change directory to /var/log using this command:cd /var/log Verify if the lastlog file is excessively large. To verify this, view the folder contents using this command:ls -lh Run this command to delete the lastlog file:rm lastlog Run this command to create a new lastlog file:touch lastlog Retry the conversion.
This issue can also occur with any kind of disk corruption that may result in inaccurate file sizes. Before converting an operating system using vCenter Converter, ensure to perform a file integrity check on the source operating system. For more information, see Performing a disk check (1004003). Performing a disk checkCollecting diagnostic information for VMware Converter使用 vCenter Converter 转换 Linux 虚拟机失败并出现错误：设备或资源繁忙 (Device or resource busy)
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
