Process Lock: There is a process on the ESX server that still has hold of a file(s) used by the VM. All's well that ends well! This meant the base disks of the VM being backed up where still locked, hence the failure when trying to consolidate. That worked perfectly! http://webinweb.net/unable-to/vmware-unable-to-access-file-since-it-is-locked-snapshot.html
In that case the solution is damn simple, migrate the virtual machine using either cold migration to another datastore or Storage vMotion. Saludes on The Odyssey of building a ligh…E. Related Posts After resetting a local profile on Windows Vista or 7 the user is always logged on with a temporary profile August 29, 2010 Windows has detected that Offline Caching Reply Jeena Me says 22 November 2010 at 12:24 pm I had the same problem and to unlock such file nothing helped but a tool available at http://pathtoodeep.com Reply Luis says
MCSA, MCSE, CCNA, Citrix CCA and ITIL certified. Now what you need to do is work out what is actually locking this file and then (unsurprisingly) find a way to unlock it. The machine's snapshot files were all removed and the machine was using its original vmdk file once again.
Great. I got into the snapshot manager window and pressed the "Delete All" button and after a few minutes a new error message appeared. You can simply add the "consolidation" tab to the VI client, find any VMs that require consolidation and kick it off: What went wrong in my case? Virtual Machine Disks Consolidation Is Needed No Snapshots As well as on this site, you can find him on Twitter and Google+ Comments Khai says 19 June 2009 at 11:52 am kill Process is file lock fuser -k Reply
Removing the base disk from the backup appliance VM was enough to remove the lock, after which consolidation was possible, and problem solved. An Error Occurred While Consolidating Disks: Could Not Open/create Change Tracking File. Normally you would expect a locked file message also when starting the VM. Bonnie Bauder says: February 22, 2013 at 02:30 Thank you! Removal of Snapshots - fix VM snapshot Given the situation that the VM can be powered on without issues, new snapshots can be created but not deleted, something strange is going
How it was fixed The solution was, as it is most of the time, simple: I manually removed the base disks from the backup VM (without deleting them from disk of This might happen under the hood but it doesn't work the same way when it is a physical server. Unable To Access File Since It Is Locked Consolidate LinkedIn Twitter grab this Send to Email Address Your Name Your Email Address Cancel Post was not sent - check your email addresses! Disk Consolidation Needed - Unable To Access File Since It Is Locked I have been working full time in IT since 2001 in 1st to 3rd line and System Administration roles.
Like mentioned before the VM is powered off and the file lock message pops up when trying to delete the snapshots. this contact form Lucky me, I got this error: So why is this occuring? Also, check out Tecumseh's posting here. 2. TRENDING: VMware VMRC: Failed to install hcmon driver You Were not connected because a duplicate name exists ... Vmware Kb Investigating Virtual Machine File Locks On Esxi/esx
Unfortunately this does not work always smoothly, as I would like to. One day I came across the "Unable to access file since it is locked" error. I wanted to make sure that is how you did it before I proceed. As always before performing anything; check, double check, test and always ensure you have a backup. http://webinweb.net/unable-to/vmware-snapshot-unable-to-access-file-since-it-is-locked.html Bryan says: July 7, 2014 at 20:53 services.sh restart from cli worked for me as well.
I found you through Google and bingo my system is back. Detected An Invalid Snapshot Configuration Search for: Posts Calendar October 2015 M T W T F S S « Aug Nov » 1234 567891011 12131415161718 19202122232425 262728293031 Recent Posts New Date for VMware’s GO Once confirmed I placed the host in maintenance mode, DRS vMotioned all VMs to another host in the cluster and restarted the hostd service. /etc/init.d/hostd restart Once the hostd service had
Mike says: August 30, 2013 at 16:31 Can someone confirm the steps for me as I've been encountering this lately. 1. The appliance powered on smoothly and I checked that the services were up and running via VDPA's console. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your Cannot Open The Disk Failed To Lock The File Share This Story, Choose Your Platform!
No No - I run my labs out in The Cloud Yes - Using dedicated hardware Yes - Running under VMware Workstation, Fusion or similar vote View Results Featured TechHead Video This can be caused by another disk with the same VMDK file name being referenced by the VM. Ben Greslick says: February 13, 2013 at 19:47 Storage VMotion to another datastore. http://webinweb.net/unable-to/vmware-unable-to-access-file-because-it-is-locked.html Request unsuccessful.
The first encounter was a failed log of VDP appliance on my e-mail inbox, but I am used to logs like this since as I said VDPA does not work always smoothly. Strange enough, also a power on works fine. CompetitionCloud and Service ProvidersVCSP Program and Product OfferingsVeeam Availability ConsoleMonitoring and ManagementVeeam ONE9.5Veeam Management Pack for System CenterFree ToolsVeeam Backup Free EditionVeeam Endpoint Backup FREEVeeam Agent for Linux FREEVeeam ONE Free When checking the virtual machine log file vmware.log in the home directory of the VM, the following entry can be found: 2015-03-05T20:08:25.112Z| vcpu-0| I120: AIOGNRC: Failed to open '/vmfs/volumes/0025909bfda0/WinVM/WinVM-flat.vmdk' : Failed
You can also subscribe without commenting. It seemed that the backup job did not delete the backup snapshot, let's wipe it out manually. I wiped it out by right clicking the vmdk file on the datastore browsing window. I restarted the VM to check that everything is ok.