Article ID: 118839, created on Nov 24, 2013, last review on Dec 15, 2014

  • Applies to:
  • Operations Automation 5.4
  • Panels
  • Virtuozzo
  • Virtuozzo containers for Linux
  • Virtuozzo hypervisor


  1. All containers on the hardware node are functioning in read-only (ro) mode.

  2. Container cannot be started:

    [root@pcs01-01 ~]# vzctl start 99
    Unable to open the lock file /vz/private/99.lck: Read-only file system
  3. Impossible to create any file on /vz

    [root@vz ~]# touch /vz/root/101/testfile
    touch: cannot touch `testfile': Read-only file system


The kernel remounted /vz partition in read-only mode because of I/O or filesystem errors.

[root@vz ~]# cat /proc/mounts | grep vz
/dev/sda2 /vz ext4 ro,noatime,barrier=1,data=ordered 0 0


1) Check /var/log/messages and dmesg for hardware errors.

Filesystem will be remounted in "read/write" after node reboot which can be a quick solution, however carefully check the logged errors before that. Important data can be copied from /vz at this point.

2) Try to perform fsck on the /vz partition.

3) If the issue reoccurs, perform fsck again and migrate the containers to another server as soon as possible.

4) Contact your hardware vendor to verify the hard drive consistency.

Search Words

core issue

Read-only file system

304 : Processing of the request was incomplete.

Storage read only

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f e8e50b42231236b82df27684e7ec0beb 0dd5b9380c7d4884d77587f3eb0fa8ef 5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 614fd0b754f34d5efe9627f2057b8642 ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF