Severity: normal

The libvirt box has problem with the default shared mode (NFS)

A fresh vagrant up from the atlas box brings:

mount -o vers=3,udp /vagrant
if command -v /sbin/init && /sbin/init --version | grep upstart; then
  /sbin/initctl emit --no-wait vagrant-mounted MOUNTPOINT=/vagrant
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified

this seens to relate to this bug in Jessie:  #775542
NFS exports fail due to rpcbind not starting before nfs-common and

 <gory technical details>
 the rpc.statd startup depends on portmapper
 portmapper is started by the rpcbind service
 and the rpcbind service is not started early enough if started at all

I see three possibility fo fix this:
 A) switch to NFSv4 by default via a Vagrant configuration option
NFSv4 does not requires the rpc.statd service to run before mounting a
NFS share
 B) force the rpcbind server to start earlier by patching stuff in /etc
 C) switch to rsync as the default file sharing mecanismus ( or maybe
p9fs) for libvirt boxes. Rsync has also the advantage of not requiring
the root password for each vagrant up.

I would propose to work this bug around in order of preferences via C) or A)

and check if #775542 is fixed in stretch

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Reply via email to