tokensolution
Cadet
- Joined
- Apr 26, 2018
- Messages
- 7
Hello, I'm a newb so I don't know where to start.
I have 3 VMs (x2 Ubuntu Server, x2 CentOS7 (RIP)) that run via NFS provided by TrueNAS over 10gig to a Xen hypervisor.
After the update all the VMs are now reporting various outputs such as OSError: [Errno 30] Read-only file system: 'var/lib/cloud/data' etc. CentOS goes on and on with
"systemd-journald[55702]: Failed to send WATCHOG=1 nofification message: Transport endpoint is not connected".
I do not have screen shots of previously setting up my NFS so I do not know where the delta is that is making this NFS to my Xen server read only now. All my VMs are down.
EDIT
It looks like adding an ACL for everyone to full control fixed the issue with the CentOS VMs, but the Ubuntu VMs are still upset. All VMs are using the same NFS dataset so I guess its an Ubuntu vs CentOS checksum thing or something.
This is the second time updating broke my NFS VM permissions. I suppose this is a low level uncommon use-case?
I have 3 VMs (x2 Ubuntu Server, x2 CentOS7 (RIP)) that run via NFS provided by TrueNAS over 10gig to a Xen hypervisor.
After the update all the VMs are now reporting various outputs such as OSError: [Errno 30] Read-only file system: 'var/lib/cloud/data' etc. CentOS goes on and on with
"systemd-journald[55702]: Failed to send WATCHOG=1 nofification message: Transport endpoint is not connected".
I do not have screen shots of previously setting up my NFS so I do not know where the delta is that is making this NFS to my Xen server read only now. All my VMs are down.
EDIT
It looks like adding an ACL for everyone to full control fixed the issue with the CentOS VMs, but the Ubuntu VMs are still upset. All VMs are using the same NFS dataset so I guess its an Ubuntu vs CentOS checksum thing or something.
This is the second time updating broke my NFS VM permissions. I suppose this is a low level uncommon use-case?
Last edited:
