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 .

Copy

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

  1. Check the hostname for the OpenStack instance.
Copy
  1. Log in to the host on which the instance resides.
  2. Navigate to the disk file location mentioned in the ostackhost.log error.
Copy
  1. Create a backup copy of the original disk file in the same directory.
Copy
  1. Rename the original disk to disk.old.
Copy
  1. Rename the backup disk to disk.
Copy
  1. Set the instance status to active.
Copy
  1. Stop the server.
Copy
  1. Start the server.
Copy
VariableType to search · ESC to discard
GlossaryType to search · ESC to discard
InsertType to search · ESC to discard
No matches
Next to read:
Image File Copied to Glance Host, Image Not Discovered

© 2025 Platform9. All Rights Reserved

On This Page
Instance in ERROR State, Write Lock on Disk FileProblemEnvironmentCauseResolution