VMdamentals.com VMware Technical Deepdive by Erik Zandboer HomeAbout « Best of VMdamentals.com 2011 posts "My VAAI is Better Than Yours" » Snapshot Consolidation needed - Which with my luck… fails February And my luck was, that selecting "consolidate" ended in that one brilliant error: Unable to access file since it is locked. 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 Then the backup was made. Source
I will not go into details which backup product this was though 🙂 So the backup solution of Brand X was trying to backup a VM. After the backup was made however, the backup solution somehow did not manage to hot-remove the disks from the backup VM. Archives Archives Select Month January 2015 (1) October 2014 (1) August 2014 (4) September 2013 (1) August 2013 (1) May 2013 (1) March 2013 (1) December 2012 (3) October 2012 (1) Of course, consolidating the snapshot did not work in my case.
All's well that ends well! Related PostsFind the ESXi that owns the VMDK lock or other file lock on a VMFS datastore Find the ESXi that owns the VMDK lock or other file lock on a Unfortunately the VM can be "powered on", "powered off" and no locked file can be found. Share This Story, Choose Your Platform!
As always before performing anything; check, double check, test and always ensure you have a backup. That is actually the first step - know about your situation! Erik Zandboer says: March 8, 2013 at 00:02 Actually in my case there was no ESXi reboot required at all. An Error Occurred While Consolidating Disks: Could Not Open/create Change Tracking File. To do this just access the CLI and type "services.sh restart" Once that is complete the consolidation should work.
The up side is it's only a lab environment. Virtual Machine Disks Consolidation Failed run consolidate 4. Register. Incapsula incident ID: 184000010219588115-810418813613375513 Request unsuccessful.
If it fails it causes only troubles. Consolidate Virtual Machine Disk Files Stuck Browsing the datastore of the VM I noticed that an old differential disk file was not deleted (it is the vmdk file that it's filename ends with a number). Latest Blog Posts Veeam CBT Data is Invalid - Reset CBT Without Powering Off VM View 7 Administrator Blank Error Dialog/Window After Upgrade App-V 5.x Writing to the native registry vSphere Saludes on The Odyssey of building a ligh…E.
But the story will end with a VMware bug, that is absolutely weird but luckily easy to fix. 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 Unable To Access File Since It Is Locked Consolidate Running ESXi 5.0u1. Disk Consolidation Needed - Unable To Access File Since It Is Locked Note: We could not see the snapshots in the snapshot manager.
Hopefully it´s not your largest virtual machine and let´s keep the fingers crossed you have enough free space on another datastore to move all VMs data. this contact form Thank you. IE http://www.veeam.com/kb1681 This should clear the snapshot(s) presentIf the Virtual Appliance mode failed to unmount hot-added disks:Remove all hot-added disks from the Veeam VMCreate one snapshot manuallyPerform a "Delete All" operation base5002 says: June 25, 2014 at 15:53 I have also had success by restarting the management services of the ESXi host in which the VM sits. Virtual Machine Disks Consolidation Is Needed No Snapshots
Thank you again and happy holidays! Strange enough, also a power on works fine. I guessed that the VDP appliance was root of the problem, so I shut it down and tried to delete all the snapshots of the problematic VM. http://webinweb.net/unable-to/vmware-snapshot-unable-to-access-file-since-it-is-locked.html Mind you that this VM is my 5.1 vCenter server so that added a little more stress.
Related Posted by Nikos Chrissostomidis in Troubleshooting Tagged: vCenter, VMware, vmware data protection, VMware vSphere Post navigation ← Upgrade VMware's vSphere Data Protection Appliance6.0 VMware Annual Event 2015 at Athens,Greece → Detected An Invalid Snapshot Configuration add the virtual disks back to the VM 5. Sign Up for opvizor Comments are closed.
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. Thank you! Designed and Hosted by Andy Barnes English Localized Websites English Deutsch Français Русский Italiano Español Nederlands 中文(简体) 日本語 Česky Polski Türkçe Português(BR) Español(LA) Resource Pages Svenska עברית Sign In Downloads Contact An Error Occurred While Consolidating Disks 5 (input/output Error) Good luck!
All Rights Reserved. Post to Cancel %d bloggers like this: This might not be the solution for me but if anyone can confirm I would appreciate it….I know this post is old and may be abandoned at this point…cheers! http://webinweb.net/unable-to/vmware-unable-to-access-file-since-it-is-locked-snapshot.html Like mentioned before the VM is powered off and the file lock message pops up when trying to delete the snapshots.
Theoretically it might be enough just to move one of the vmdk files of the virtual machine, but we didn´t checked that so far. 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