Hi all,
We are experiencing a really annoying issue. From time to time and apparently without a reason (or we are not able to see it) all our Linux VM enter in read-only mode. The only way to get it work is restarting the VM with a LiveCD and executing a fsck over the filesystem. VM with Windows do work properly.
These are our specifications:
-> Proxmox : Proxmox 6.4.13
-> VM:
- OS: Ubuntu 18.04
- / mountpoint: is a ZFS Mirror disk. This partition (/) is around 25GB and when this issue happens it is 60% free. LVM activated.
Reviewing system logs, kernel messages, journalctl and our own monitoring systems, it has come to our attention that this issue is closely related with Proxmox Backup Server tasks. In our case, if a backup is frozen or if we stop the backup task manually, somehow, system gets corrupt and enters in read only mode. We are unsure if problem comes from a backup frozen (perhaps by a high I/O) or the cause is stopping manually the backup.
Backing up the system is a must for us, but at this moment we do not trust totally the backup mechanism as looks like it is affecting filesystem. But we are not sure about this diagnosis.
May you be so kind as to help us to find the cause of this behaviour?
We are experiencing a really annoying issue. From time to time and apparently without a reason (or we are not able to see it) all our Linux VM enter in read-only mode. The only way to get it work is restarting the VM with a LiveCD and executing a fsck over the filesystem. VM with Windows do work properly.
These are our specifications:
-> Proxmox : Proxmox 6.4.13
-> VM:
- OS: Ubuntu 18.04
- / mountpoint: is a ZFS Mirror disk. This partition (/) is around 25GB and when this issue happens it is 60% free. LVM activated.
Reviewing system logs, kernel messages, journalctl and our own monitoring systems, it has come to our attention that this issue is closely related with Proxmox Backup Server tasks. In our case, if a backup is frozen or if we stop the backup task manually, somehow, system gets corrupt and enters in read only mode. We are unsure if problem comes from a backup frozen (perhaps by a high I/O) or the cause is stopping manually the backup.
Backing up the system is a must for us, but at this moment we do not trust totally the backup mechanism as looks like it is affecting filesystem. But we are not sure about this diagnosis.
May you be so kind as to help us to find the cause of this behaviour?