Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
Committing Dynamically Added .REDO Logs after Virtual Machine Crashes or Is Forcefully Terminated
Details
The virtual machine later crashed or was killed (not powered off). How do I commit the .REDO logs in this situation?
Solution
Note: This problem does not affect the .REDO logs that are automatically added to disks in nonpersistent, undoable or append mode.
To use vmkfstools to apply the dynamically added .REDO logs to a virtual disk:
- Log onto the service console as root.
- Identify the .REDO logs associated with the affected virtual disk:
ls /vmfs/VMFSVolName/My-VM.dsk*
/vmfs/VMFSVolName/My-VM.dsk
/vmfs/VMFSVolName/My-VM.dsk.REDO - Run vmkfstools to commit the .REDO log to the parent disk:
vmkfstools --commit /vmfs/VMFSVolName/My-VM.dsk.REDO
This will commit My-VM.dsk.REDO to its parent disk.
Commit it (y/n) ? y - Confirm that vmkfstools successfully committed and deleted the .REDO log:
ls /vmfs/VMFSVolName/My-VM.dsk*
/vmfs/VMFSVolName/My-VM.dsk
When all dynamically added .REDO logs have been committed, the virtual machine is ready to power on.
Prior to starting a crashed or forcibly terminated virtual machine, you must use vmkfstools to commit dynamically added .REDO logs; if you do not, their contents become unrecoverable.
Keywords
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
Actions
KB:
- Updated:
- Categories:
- Product Family:
- Product(s):
- Product Version(s):

