| Previous | Next |
| ESPIPE | EMLINK |
EROFS
What a read-only filesystem result means
EROFS is returned when the operation would modify an object through a read-only filesystem view. The restriction can be intentional, for example a recovery image, immutable deployment layer, read-only bind mount, or media that was mounted without write access. It can also be protective: some filesystem and storage configurations switch or remain read-only after detecting an error to avoid making damage worse.
Changing file permissions cannot solve this condition because the decision is made at the mount or backing-store layer, before normal inode write permission is relevant. Overlay and container environments need special care: a path visible to the process may resolve to a lower read-only layer when the expected writable upper layer is absent or full.
How to investigate
- Identify the exact mount for the target path and inspect its options, backing device, and overlay layers.
- Review kernel and storage logs for I/O, journal, or filesystem errors near the first failure.
- Confirm that the application writes to its designated data path rather than an installation or image layer.
- Do not remount read-write blindly after a protective transition; diagnose the storage or filesystem condition first.
References
Looking for a different code? Search another status or error code.