| Summary: | rpc-statd doesn't implement remote-fs-pre.target | ||
|---|---|---|---|
| Product: | systemd | Reporter: | Vitaly Kirsanov <krokoziabla> |
| Component: | general | Assignee: | systemd-bugs |
| Status: | RESOLVED INVALID | QA Contact: | systemd-bugs |
| Severity: | normal | ||
| Priority: | medium | CC: | krokoziabla |
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
journalctl: NFS fstab mount BEFORE rpc-statd
Wants=remote-fs-pre.target added to rpc-statd.service |
||
Created attachment 90477 [details]
Wants=remote-fs-pre.target added to rpc-statd.service
I'm not sure if this is the most correct solution for the problem (but at least it does the trick) because I don't know how systemd unit files are produced (by systemd or maybe by deamons' designers).
I've learnt that rpc-statd.target is provided by the designers of nfs-utils. So now I think the best place to report this bug is http://bugzilla.kernel.org/ I've created a bug report on bugzilla.linux-nfs.org https://bugzilla.linux-nfs.org/show_bug.cgi?id=237 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 90476 [details] journalctl: NFS fstab mount BEFORE rpc-statd sytemd version: 208 Symptoms: - systemd cannot mount an NFS share from /etc/fstab during during booting (which used to be mounted without a problem under OpenRC). But if later I run 'systemctl start sharename.mount' the share mount well. OS: - Gentoo and ArchLinux (exactly the same behaviour) What I've gathered: journalctl shows that systemd tries to bring up remote-fs.target and all its dependencies (including the NFS share) BEFORE it proceeds to starting up rpc-statd daemon. I examined /usr/lib/systemd/system/rpc-statd.target file and learnt that there was 'Before=remote-fs-pre.target' but no 'Wants=remote-fs-pre.target'. And systemd.special(7) manual says that remote-fs-pre.target is a passive target and must be pulled in by the provider rather than the consumer of the target. I added this line to /usr/lib/systemd/system/rpc-statd.target and got the correct order of starting (i.e. the share got mounted after rpc-statd had completed launching). I've attached the full journalctl output for one boot sequence. The share name is '/sugar'