---
name: openshift-ts-storage-file-readonly
title: Why are the file systems for worker nodes changed to read-only?
description: Troubleshoot file storage volumes that become read-only.
last-updated: 2026-08-12
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/openshift?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why are the file systems for worker nodes changed to read-only?
{: #readonly_nodes}
{: support}

Troubleshoot file storage volumes that become read-only.
{: shortdesc}

[Classic infrastructure]{: tag-classic-inf}




You might see one of the following symptoms:
{: tsSymptoms}

- When you run `oc get pods -o wide`, you see that multiple pods that are running on the same worker node are stuck in the `ContainerCreating` state.
- When you run a `oc describe` command, you see the following error in the **Events** section: `MountVolume.SetUp failed for volume ... read-only file system`.

The file system on the worker node is read-only.
{: tsCauses}

Back up your data and reload your worker node.
{: tsResolve}

1. Back up any data that might be stored on the worker node or in your containers.

1. For a short-term fix to the existing worker node, reload the worker node.

    ```sh
    ibmcloud oc worker reload --cluster CLUSTER_NAME --worker WORKER_ID
    ```
    {: pre}

For a long-term fix, [update the flavor of your worker pool](https://cloud.ibm.com/docs/openshift?topic=openshift-update&format=markdown#machine_type).