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 This is what had happened: A single snapshot had been deleted on a VM The disk consolidation needed warning was shown afterwards VM -> Snapshot -> Consolidate fails with locked file Of course, consolidating the snapshot did not work in my case. That worked perfectly! Source
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). A little history: As I was testing a third party solution of "Brand X", this error occured. If it fails it causes only troubles. Pressing the "Consolidate" button did not solved the problem neither. It seemed that the problem is bigger than I first thought.
Great. Thanks, ( REPLY ) SteveJanuary 29th, 2013 - 15:53 Thnak you very much, This happened to me once before but I forgot about the mounted discs on the VEEAM proxy vm. Incapsula incident ID: 108001310283973253-849093916072085557 Toggle navigation HomeVMwareMicrosoftCitrixLinuxStorageNetworkingOtherAbout Home Resources ESX and ESXi Server Disk Consolidation Needed - Unable to access file since it is locked After deleting snapshots on a VM Good luck!
tail -f /var/log/hostd.log I then ran the following command to locate which host(s) had the lock on the VMDK stated in hostd.log vmkfstools -D /vmfs/volumes/yourvolume/yourVM/yourlockedVM.vmdk I could see a single entry for This was the causing trouble virtual disk. Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are Virtual Machine Disks Consolidation Is Needed No Snapshots Sign Up for opvizor Comments are closed.
However the consolidate operation may fail again, if the issue which caused the snapshot deletion operation to fail disk consolidation previously has not been cleared. It has been a good But bugs come typically with weird situations. Thank you again and happy holidays! After the backup was made however, the backup solution somehow did not manage to hot-remove the disks from the backup VM.
Then I powered on the Data Protection Appliance but it failed to boot up correctly with the following error: This was the root of the problem, VDP appliance had mounted the problematic The up side is it's only a lab environment. Unable To Access File Since It Is Locked Consolidate 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. Disk Consolidation Needed - Unable To Access File Since It Is Locked I am new Veeam Backups.Please help me. ( REPLY ) ShaikDecember 25th, 2013 - 13:20 Thanks, it worked for me.
Why is it locked? http://webinweb.net/unable-to/vmware-snapshot-unable-to-access-file-since-it-is-locked.html Here's what was wrong! Job automation is good when it does not fail! In my case it was Avamar holding the vmdk, but same reason. ( REPLY ) Leave a Reply Cancel reply No trackbacks yet. An Error Occurred While Consolidating Disks: Could Not Open/create Change Tracking File.
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 Unfortunately the VM can be "powered on", "powered off" and no locked file can be found. Note: We could not see the snapshots in the snapshot manager. http://webinweb.net/unable-to/vmware-remove-snapshot-unable-to-access-file.html Then I noticed an error message on my vCenter client saying "virtual machine disks consolidation needed".
Share This Story, Choose Your Platform! Detected An Invalid Snapshot Configuration Running ESXi 5.0u1. This might happen under the hood but it doesn't work the same way when it is a physical server.
LinkedIn Twitter grab this Send to Email Address Your Name Your Email Address Cancel Post was not sent - check your email addresses! But the next step is to delete the Snapshots and one of the meanest situations are locked files that stop you from doing so.# There are many different kinds of locking 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 5 (input/output Error) 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.
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. The delta files follow the directory, but now you can successfully Snapshot -> Consolidate, and the delta files will go away. Request unsuccessful. http://webinweb.net/unable-to/vmware-unable-to-access-file-since-it-is-locked-snapshot.html Well, you can find out by following the instructions in VMware KB 10051 but I my case it was simple.
Yes, when my Veeam was a VM appliance mode system I could go to this server and see disks mounted from the VMs being backed up but not any more. I wanted to make sure that is how you did it before I proceed. I restarted the VM to check that everything is ok. Daco says: September 15, 2014 at 09:31 Hi, In my case vSphereDataProtection was holding the disk.