Bug#622394: systemd: nfs-common and rpcbind unit files to fix systemd NFS issues properly
On 07/11/14 19:42, Simon McVittie wrote:
> On 07/11/14 14:57, Chris Butler wrote:
>> Not sure that's the case. The systems where I was seeing the problem
>> are running:
>>
>> ii nfs-common 1:1.2.8-9
>> ii systemd 215-5+b1
>
> Your fstab says:
Sorry, I'm mixing up the various people reporting related but distinct
symptoms. That was Matthew's fstab.
For an attempt at more clarity, here are the distinct sets of symptoms
that have been reported. Please correct me if I'm wrong on any of these.
Bug A, reported by Alban Browaeys, present in 1:1.2.3-2: "systemd[1]:
Found ordering cycle on basic.target/start" and an unbootable system. I
believe newer systemd and/or nfs-common have probably fixed this, so
#622394 should probably have been closed, and the other symptoms should
probably have had distinct bug numbers.
Bug M1, reported by Matthew Grant, present in 1:1.2.8-6: "NFS mounts
from /etc/fstab do not work". (What symptoms? What error messages?) This
one might be related to NFS entries in /etc/fstab that don't have _netdev.
Bug M2, reported by Matthew Grant, present in 1:1.2.8-6: "NFS exports
also fail due to rpcbind not starting before nfs-common and nfs-
kernel-server".
Bug C1, sort-of-reported by Chris Butler, present in 1:1.2.8-9: "the
boot order problem on NFS clients that mount remote filesystems on
boot". This might be the same thing as M1. (Do you have _netdev in the
options of the relevant mounts?)
Bug C2, reported by Chris Butler, present in 1:1.2.8-9 with Matthew's
systemd units added: 'tries to start "statd" before "rpcbind"'. I
believe this is an omission in one of Matthew's systemd units, and I am
about to test a version of nfs-common that should fix that bit.
S
Reply to: