Bug#622394: systemd: nfs-common and rpcbind unit files to fix systemd NFS issues properly
(Please keep the bug in Cc when replying to a bug, so it goes into the
bug record for other developers to refer to.)
On 07/11/14 14:57, Chris Butler wrote:
> > I think both of these might have been fixed by some combination
> > of fixing #510528, and changes in systemd v214 improving support
> > for rcS?
>
> 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
[...]
> It seemed like systemd had no idea that it needed to start the
> NFS client services before mounting NFS filesystems, and was
> instead running the two jobs in parallel. It happened to work
> 9 times out of 10 (I guess if the services started up quickly
> enough), but not always.
Your fstab says:
#shalom:/src /media/src nfs noauto,defaults,user,exec 0 0
#shalom:/home /media/home nfs noauto,defaults,user,exec 0 0
#en-gedi:/home /srv/home nfs
noauto,async,_netdev,soft,intr,defaults,exec 0 0
I notice in particular that /media/src and /media/home do not have
_netdev in the options field. That's probably why systemd can't tell
they are network devices (although, arguably, it should be able to guess
that by hard-coding knowledge that nfs is a networked filesystem -
there's been some discussion of that on the systemd mailing list).
Are your boot problems always with /media/src and /media/home, and never
with /srv/home? I'll try removing _netdev from my client VM's fstab and
trying again.
S
Reply to: