Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Why does it happen?

The default behavior or on many Linux operating systems is to set a file system to read-only if critical information can't be written to disk. If this happens the file system is corrupt and fsck has to be run to fix it. The default behavior can be changed but it is not advisable. If it is changed to "continue" errors can accumulate and corrupt the file system. If it is changed to "panic" the system will halt and fsck will need to be run on the file system before it can be restarted.

...

The following command can be run to find read-only file system systems in your instance.

grep "\sro[\s,]" /proc/mounts

...

Run fsck on the file device you wish to check. You may be prompted.

fsck /dev/vdb1

Normally, the file system is consistent, and the fsck command merely reports on the number of files, used blocks, and free blocks in the file system. If the file system is inconsistent, the fsck command displays information about the inconsistencies found and prompts you for permission to repair them.

...