The VM would not boot this morning and had the error cannot read vmdk.... "Too Many Levels of Redo files"
The following sysmtoms occurred to a VM on an ESX Host
• Last change was a commvault update on Tuesday.
• The file server required a reboot after the update.
• The reboot was o scheduled for 4 Am this morning (Friday)
• According to the performance dataThe server fell over at 904pm yesterday evening. (Thursday) so the scheduled reboot never occurred.?
• There are 3 redo files from the 17th
• And 100 redo files started to be created at 8pm yesterday According to the performance data the server fellover at 9 but the redo files continued to be created up until 7am this morning.
The server created 100 or so redo files. I am currently cloning the individual hard drives according to.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100454...
I am hoping this will resolve the issue.
I would be interested in alternative resolutions and also information about the redo process. Specifically my questions are?
Could I have deleted the redo files?
Is there a command to commit the redo files without having to clone?
Is there a log that references all of the files.?
I have read a couple of articles pertaining to earlier versions of ESX but they no longer seem to be relevant. for examle the vmware-cmd -commit and vmkfstools did not seem to do anything or were no longer valid commands.
Is there a source of knowledge on the commands and the process that relates to ESX 3.5
Many thanks!!
