Article ID: 118135, created on Oct 23, 2013, last review on May 10, 2014

  • Applies to:
  • Virtuozzo

Symptoms

All running containers on the server are mounted in read-only mode after network outage or problems with Cloud Storage:

[root@pcs ~]# grep ploop /proc/mounts
/dev/ploop10540p1 /vz/root/5527468 ext4 ro,relatime,barrier=1,data=ordered,balloon_ino=12,pfcache_csum,pfcache=/vz/pfcache 0 0
/dev/ploop27958p1 /vz/root/1011945 ext4 ro,relatime,barrier=1,data=ordered,balloon_ino=12,pfcache_csum,pfcache=/vz/pfcache 0 0
/dev/ploop56494p1 /vz/root/1552693 ext4 ro,relatime,barrier=1,data=ordered,balloon_ino=12,pfcache_csum,pfcache=/vz/pfcache 0 0
/dev/ploop33338p1 /vz/root/9332910 ext4 ro,relatime,barrier=1,data=ordered,balloon_ino=12,pfcache_csum,pfcache=/vz/pfcache 0 0

Option "ro" stands for "read-only".

Cause

Cloud Storage was unavailable for the server, which caused failed ext4 operations inside containers, and they were forced to remount in read-only mode as a result in order not to lose any data.

Resolution

The only solution is to restart these containers. To do this for all containers at once, the 'vz' service can be restarted:

# service vz restart

Search Words

ro

pstorage

read-only

0dd5b9380c7d4884d77587f3eb0fa8ef 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF