RHEL VMs File system RO state after storage failover

BobI — Wed, 04 Jun 2025 11:17:46 GMT

We had an issue the other where our storage triggered failover between controllers.

During that process our Linux based VMs went in to read-only drive state (/vol/log) to avoid data loss or corruption.

grep ro, /proc/mounts

/dev/mapper/vg_one-lv_varlog /var/log ext4 ro,seclabel,relatime,barrier=1,data=ordered 0 0

This prevents the server from functioning, we can not su to "root", thus a reboot is necessary.

This does not affect Windows VMs or RHEL VMs that are stored on datastore via FC.

Our setup

Here is our setup:

NetApp Storage FAS8200- dual controller configured for HA running Ontap 9.5P4

ESXi - 6.5 datastore mounted via NFS

Redhat version 3.10.0-1062.9.1.el7.x86_64

Any assistance would be greatly appreciated.

Re: RHEL VMs File system RO state after storage failover

paul_stejskal — Tue, 03 Mar 2020 16:35:08 GMT

Have you opened a ticket with Redhat? I don't think a failover would cause any kind of corruption like that, but there isn't a way for me to begin to know your storage system and check logs. If you're concerned, feel free to open a case. I really don't think storage would be to blame here.

topic Re: RHEL VMs File system RO state after storage failover in ONTAP Hardware

RHEL VMs File system RO state after storage failover

Re: RHEL VMs File system RO state after storage failover