Instance in ERROR State, Write Lock on Disk File
Problem
The OpenStack instance fails to start and goes in ERROR state because of a write lock on the disk file of the instance. The following error can be seen in the ostackhost.log .
Environment
- Platform9 Managed OpenStack - v3.6.0 and Higher
Cause
Another process on the host is performing I/O operations on the disk file which causes the instance to fail during the start process as it cannot get a write-lock on the disk file.
Resolution
- Check the hostname for the OpenStack instance.
- Log in to the host on which the instance resides.
- Navigate to the disk file location mentioned in the ostackhost.log error.
- Create a backup copy of the original disk file in the same directory.
- Rename the original disk to disk.old.
- Rename the backup disk to disk.
- Set the instance status to active.
- Stop the server.
- Start the server.
Was this page helpful?