Hello,
i have testing Proxmox 4.4 currently connected via NFS3 to our storage NFS HA cluster. If we create situation when storage is out (just stopped NFS for enough time), VMs are going broken, for example one of the situation:
1] freeipa VM - services crash, fs=rw, so reboot VM -> ldap database broken
2] freeipa VM - services crash, fs=rw, restart services -> nothing broken
3] VM - fs=ro, hard reset -> fs damaged
VMs setup:
cache - default(no cache)
disk - virtual scsi, ext4
NFS server:
vm storage - option sync
I saw, that after some time usually VMs are going to fs=ro and those problems probably has some point in VM RAM caching before syncing with fs (on proxmox? on nfs?), but still, too much problems. I just dont understand, how VM hardreset can damage fs for example...It looks as unreliable even with different type network storage if there will be an outage...
Why we see so much damage and what is best way to handle outage in view of the VMs? Or, where is the main problem?
i have testing Proxmox 4.4 currently connected via NFS3 to our storage NFS HA cluster. If we create situation when storage is out (just stopped NFS for enough time), VMs are going broken, for example one of the situation:
1] freeipa VM - services crash, fs=rw, so reboot VM -> ldap database broken
2] freeipa VM - services crash, fs=rw, restart services -> nothing broken
3] VM - fs=ro, hard reset -> fs damaged
VMs setup:
cache - default(no cache)
disk - virtual scsi, ext4
NFS server:
vm storage - option sync
I saw, that after some time usually VMs are going to fs=ro and those problems probably has some point in VM RAM caching before syncing with fs (on proxmox? on nfs?), but still, too much problems. I just dont understand, how VM hardreset can damage fs for example...It looks as unreliable even with different type network storage if there will be an outage...
Why we see so much damage and what is best way to handle outage in view of the VMs? Or, where is the main problem?