I updated my 13.1 office desktop last week, I saw somebody mention a
new 3.12 kernel. On start-up, it now claims one of two NFS drives
couldn't be mounted, although in fact they were both mounted. This
caused postfix and X not to be started. I commented out of the mounts
in /etc/fstab and rebooted, now it worked.
As 13.1 is out of maintenance, I guess I'm on the right list?
office11:~ # systemctl status home-london.mount
home-london.mount - /home/london
Loaded: loaded (/etc/fstab)
Active: failed (Result: exit-code) since Wed 2016-03-16 09:00:15 CET; 1min
Process: 2712 ExecMount=/bin/mount -n -t nfs -o v3,rsize=8192,wsize=8192,fsc
fileserver:/home/london /home/london (code=exited, status=32)
Mar 16 09:00:15 office11 mount: Starting rpc.statd .....done
Mar 16 09:00:15 office11 systemd: home-london.mount mount process exited,
Mar 16 09:00:15 office11 systemd: Failed to mount /home/london.
Mar 16 09:00:15 office11 systemd: Unit home-london.mount entered failed
Mar 16 09:00:15 office11 mount: mount.nfs: rpc.statd is not running but
is required for remote locking.
Mar 16 09:00:15 office11 mount: mount.nfs: Either use '-o nolock' to keep
locks local, or start statd.
Mar 16 09:00:15 office11 mount: mount.nfs: an incorrect mount option was
Looks like a timing issue wrt rpc.statd ? On one boot-up it'll be
/home/london, on another it'll be /home/barcelona
Per Jessen, Zürich (2.4°C)
http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
Evergreen mailing list