[systemd-bugs] [Bug 72493] New: rpc-statd doesn't implement remote-fs-pre.target
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Dec 8 11:04:48 PST 2013
https://bugs.freedesktop.org/show_bug.cgi?id=72493
Priority: medium
Bug ID: 72493
Assignee: systemd-bugs at lists.freedesktop.org
Summary: rpc-statd doesn't implement remote-fs-pre.target
QA Contact: systemd-bugs at lists.freedesktop.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: krokoziabla at gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: general
Product: systemd
Created attachment 90476
--> https://bugs.freedesktop.org/attachment.cgi?id=90476&action=edit
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'
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20131208/78d794e3/attachment-0001.html>
More information about the systemd-bugs
mailing list