[CentOS-devel] Vagrant centos/7 v1811.01 breaks nfs at boot
Laurențiu Păncescu
lpancescu at centosproject.orgSat Jan 12 21:24:28 UTC 2019
- Previous message: [CentOS-devel] Vagrant centos/7 v1811.01 breaks nfs at boot
- Next message: [CentOS-devel] Vagrant centos/7 v1811.01 breaks nfs at boot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi John-Paul, I think you have a more generic problem, not something affecting just the Vagrant images. On 2019-01-11 22:19, John-Paul Robinson wrote: > It seems that the latest vagrant box for centos/7 is breaking nfs > mounts at boot. My vagrant project has an nfs server and client > node. The client has two nfs mount in fstab. > https://gitlab.rc.uab.edu/jpr/ohpc_vagrant > > Using the image from the prior release (1804.02, kernel > 3.10.0-862.2.3.el7.x86_64, CentOS Linux release 7.5.1804 (Core) ) the > mounts complete successfully. The newest releases (1811.02 and > 1809.01) fail to mount the drives at boot. We'll go back to using XFS in starting with 1812, but I wouldn't rely on timing to see if NFS is going to work or not - that's too fragile. I wasn't able to find an fstab in the Ansible playbooks your repo points to, perhaps you could provide a direct link? Are you already using the _netdev mount option in your fstab? That should make sure that these mounts are only attempted after the network is working. This should be mentioned by 'man systemd-mount', didn't use NFS myself though. Best regards, Laurențiu
- Previous message: [CentOS-devel] Vagrant centos/7 v1811.01 breaks nfs at boot
- Next message: [CentOS-devel] Vagrant centos/7 v1811.01 breaks nfs at boot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS-devel mailing list