> Cannot Remove
> Cannot Remove Delta.vmdk Device Or Resource Busy
Cannot Remove Delta.vmdk Device Or Resource Busy
Just helped me to avoid rebooting all hosts in my cluster Reply Anonymous says: January 27, 2014 at 06:08 Hi guys, you can also check out Powergui. This host is identified by the MAC address of the primary Service Console interface.Note:Locked files can also be caused by backup programs keeping a lock on the file while backing up To check for Service Console-based locks on non-ESXi servers, run this command: # lsof | grepYou will see an output similar to:COMMAND PID USER FD TYPE DEVICE SIZE Removing the .lck file (NFS Only)Thefiles on the virtual machinemay be locked via NFS storage. this content
The output will be similar to:/vmfs/volumes///.vmxNote: Record this information as it is required in the remainder of this process. Another thing to check is if any snapshots are preventing you to delete this file. In such cases, if the backup fails and/or the host shuts down, the backup virtual machine may still have another virtual machine's vmdk file(s) attached. Powering on a virtual machine fails.
As such, the command can be used to test the file and directory locking mechanism in the VMFS filesystem, where the procedure is expected to fail on locked files. Its free. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the Have a look.
To address this issue, seeTroubleshooting a virtual machine that has stopped responding (1007819).If the output from this command isgetstate() = off, the ESX host may be unaware of the file lock.For From the above example, the process ID is3631:# kill 3631Warning:Using the kill command will abruptly terminate all the running process for the virtual machine without generating any core dump to analyze Very helpful to me. Register Name * Username * Email Address * Confirm email Address * Password * Confirm Password * Security Code; * Fields marked with an asterisk (*) are required.
fuser -u /path-to-filename.vmdk show which user and pid access that vmdk file. 0 Message Author Comment by:rastafaray2011-08-28 Comment Utility Permalink(# a36445648) i dont think fuser is installed on ESXi You can identify this by files denoted with .lck.#### (where #### refers to the World ID that has the file lock) at the end of the filename. In this example, the MAC address of the Service Console orvswif0interface of the offending ESX Server is00:13:72:66:E2:00. my review here You may pressG, once open, to immediately scroll to the bottom of the log's output.
For example, Console OS troubleshooting methods such as using the lsof utility are not applicable to VMware ESXi hosts.Start with identifying the server whose VMkernel may be locking the file. Nevertheless there seems to be a process holding a file handle to these two files. Now try and delete the file that was locked. Like Show 0 Likes (0) Actions 3.
Press c to add the column for the Leader World ID. In certain circumstances these locks may not be released when the virtual machine is powered off. http://www.powergui.org/downloads.jspa This will also show you orphaned files. Identify the target virtual machine by its Name and Leader World ID (LWID).
Adding an existing disk (VMDK) to a virtual machine that is already powered on fails with the error: Failed to add disk scsi0:1. news If this is the case, collect diagnostic information from the VMware ESX host and submit a support request. For servers prior to VMware ESX/ESXi 4.1, this command writes the output of the above command to the system's logs. A Device or resource busy message is printed for each virtual machine that is running but not registered to this ESX host.
This is thereferenced in the remainder of the article. Forgot your password? Reply Anonymous says: February 26, 2013 at 03:01 You can view this guide . have a peek at these guys For example, Console OS troubleshooting methods such as using thelsofutility are not applicable to VMware ESXi hosts.Start with identifying the server whose VMkernel may be locking the file.
What can I do to prevent this in the future? If the vmdk is an orphan then one of the ESX hosts will be locking the file. Fill in your details below or click an icon to log in: Email (Address never made public) Name Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using
One way of doing this is: ./sbin/services.sh restart share|improve this answer edited Feb 4 '15 at 20:02 Community♦ 1 answered Feb 14 '13 at 5:11 Daniel t. 5,57811527 I
Using the touch utility to determine if the file can be lockedThe touch utility is designed to update the access and modification time stamp of the specified file or directory. This is an NFS file lock and is only listed when using thels -lacommand as it is hidden file.Caution: These can be removed safely only if the virtual machine is not Failed to power on scsi0:1 When powering on the virtual machine, you see one of these errors: Unable to open Swap File Unable to access a file since it is locked Press c to switch to the CPU resource utilization screen.
You may have to set DRS to manual to ensure thatthe virtual machine powers on the correct host.If the virtual machine still does not get powered on, complete these procedures while If a host can be determined however the specific offending VMkernel child process ID cannot be identified, the server requires rebooting to clear the lock.Note: You can also try to migrate Nullam est ligula, fringilla at auctor et, fermentum nec turpis. check my blog To identify the server: Report the MAC address of the lock holder by running the command (except on NFS volume): # vmkfstools -D /vmfs/volumes///Note: Run this command on
The vmkernel log indicates that the MAC address of the owner identifier is all zeros, the last 12 zeros preceding mtime. Remove one of the disk from the VM and attempt to power on.Opening a Support RequestIf your problem still exists after attempting the steps in this article, contact VMware Technical Support After logging into the server, the process maintaining the lock can be analyzed.Note: If this process does not reveal the MAC address, or the owner identifier is all zeroes, it is At the World to kill prompt, type in the Leader World ID from step 5 and press Enter.
If there are any issues with the backup it may result in the lock not being removed correctly.In some cases you may need to disable your backup application or reboot the If the message is reported, proceed to the next section.If another error message is reported, it may indicate that the metadata pertaining to file or directory locking on VMFS may not I rebooted the host, but now cannot delete the file. (I renamed it to BADFILE). Each line contains the datastore and location within of a virtual machine's .vmx file.
does this help? 0 LVL 5 Overall: Level 5 VMware 1 Message Expert Comment by:smangogna2011-08-29 Comment Utility Permalink(# a36446054) Try to restar managment services 0 LVL 5 Overall: Level This is the referenced in the remainder of the article.