<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - rpc-statd doesn't implement remote-fs-pre.target"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72493">72493</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>rpc-statd doesn't implement remote-fs-pre.target
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>krokoziabla@gmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=90476" name="attach_90476" title="journalctl: NFS fstab mount BEFORE rpc-statd">attachment 90476</a> <a href="attachment.cgi?id=90476&action=edit" title="journalctl: NFS fstab mount BEFORE rpc-statd">[details]</a></span>
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'</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>