1 |
On Wed, Sep 26, 2012 at 8:11 AM, walt <w41ter@×××××.com> wrote: |
2 |
> On 09/25/2012 08:21 PM, Canek Peláez Valdés wrote: |
3 |
> |
4 |
>> Do |
5 |
>> you need remote filesystem support? If not, then don't worry about it; |
6 |
>> but if you want to find the problem, send the output from systemctl |
7 |
>> status remote-fs.target. Mine is: |
8 |
>> |
9 |
>> # systemctl status remote-fs.target |
10 |
>> remote-fs.target - Remote File Systems |
11 |
>> Loaded: loaded (/usr/lib64/systemd/system/remote-fs.target; |
12 |
>> enabled) |
13 |
>> Active: active since Mon, 24 Sep 2012 18:33:09 -0500; 1 day and |
14 |
>> 3h ago |
15 |
>> Docs: man:systemd.special(7) |
16 |
> |
17 |
> |
18 |
> I mount /usr/portage by nfs, so I do want remote-fs support. |
19 |
> |
20 |
> The problem is listed by journalctl: |
21 |
> |
22 |
> Sep 26 05:44:27 a6v rpc.statd[1658]: Running as root. chown /var/lib/nfs to |
23 |
> choose different user |
24 |
> Sep 26 05:44:27 a6v rpc.statd[1658]: failed to create RPC listeners, exiting |
25 |
> Sep 26 05:44:27 a6v mount[1655]: mount.nfs: rpc.statd is not running but is |
26 |
> required for remote locking. |
27 |
> Sep 26 05:44:27 a6v mount[1655]: mount.nfs: Either use '-o nolock' to keep |
28 |
> locks local, or start statd. |
29 |
> Sep 26 05:44:27 a6v mount[1655]: mount.nfs: an incorrect mount option was |
30 |
> specified |
31 |
> Sep 26 05:44:27 a6v systemd[1]: usr-portage.mount mount process exited, |
32 |
> code=exited status=32 |
33 |
> Sep 26 05:44:27 a6v systemd[1]: Failed to mount /usr/portage. |
34 |
> Sep 26 05:44:27 a6v systemd[1]: Dependency failed for Remote File Systems. |
35 |
> Sep 26 05:44:27 a6v systemd[1]: Job remote-fs.target/start failed with |
36 |
> result 'dependency'. |
37 |
> Sep 26 05:44:27 a6v systemd[1]: Unit usr-portage.mount entered failed state. |
38 |
> |
39 |
> |
40 |
> # systemctl status remote-fs.target |
41 |
> remote-fs.target - Remote File Systems |
42 |
> Loaded: loaded (/usr/lib64/systemd/system/remote-fs.target; |
43 |
> enabled) |
44 |
> Active: inactive (dead) |
45 |
> Docs: man:systemd.special(7) |
46 |
> |
47 |
> # grep nfs /etc/fstab |
48 |
> a6:/usr/portage /usr/portage nfs rw,auto 0 0 |
49 |
> (BTW, this works correctly when booting with openrc.) |
50 |
> |
51 |
> Any hints would be much appreciated, thanks. |
52 |
|
53 |
I believe you have your answer: |
54 |
|
55 |
> Sep 26 05:44:27 a6v mount[1655]: mount.nfs: rpc.statd is not running but is |
56 |
> required for remote locking. |
57 |
> Sep 26 05:44:27 a6v mount[1655]: mount.nfs: Either use '-o nolock' to keep |
58 |
> locks local, or start statd. |
59 |
|
60 |
Put nolock in the mount options in fstab (rw,auto,nolock), or get |
61 |
rpc.statd running. For the later, you will need the service file for |
62 |
it: a quick googling turned out: |
63 |
|
64 |
http://en.gentoo-wiki.com/wiki/Systemd#NFS |
65 |
|
66 |
Put the necessary service files in /etc/systemd/system, make a link to |
67 |
them in /etc/systemd/system/remote-fs.target.wants (you need to do |
68 |
this by hand, since they don't seem to have an [Install] section), and |
69 |
then do a 'systemctl --system daemon-reload'. Afterwards, you should |
70 |
be able to mount your NFS partition with 'systemctl start |
71 |
usr-portage.mount'. |
72 |
|
73 |
Regards. |
74 |
-- |
75 |
Canek Peláez Valdés |
76 |
Posgrado en Ciencia e Ingeniería de la Computación |
77 |
Universidad Nacional Autónoma de México |