On Wed, Sep 26, 2012 at 8:11 AM, walt <w41...@gmail.com> wrote:
> On 09/25/2012 08:21 PM, Canek Peláez Valdés wrote:
>
>>  Do
>> you need remote filesystem support? If not, then don't worry about it;
>> but if you want to find the problem, send the output from systemctl
>> status remote-fs.target. Mine is:
>>
>> # systemctl status remote-fs.target
>> remote-fs.target - Remote File Systems
>>           Loaded: loaded (/usr/lib64/systemd/system/remote-fs.target;
>> enabled)
>>           Active: active since Mon, 24 Sep 2012 18:33:09 -0500; 1 day and
>> 3h ago
>>             Docs: man:systemd.special(7)
>
>
> I mount /usr/portage by nfs, so I do want remote-fs support.
>
> The problem is listed by journalctl:
>
> Sep 26 05:44:27 a6v rpc.statd[1658]: Running as root.  chown /var/lib/nfs to
> choose different user
> Sep 26 05:44:27 a6v rpc.statd[1658]: failed to create RPC listeners, exiting
> Sep 26 05:44:27 a6v mount[1655]: mount.nfs: rpc.statd is not running but is
> required for remote locking.
> Sep 26 05:44:27 a6v mount[1655]: mount.nfs: Either use '-o nolock' to keep
> locks local, or start statd.
> Sep 26 05:44:27 a6v mount[1655]: mount.nfs: an incorrect mount option was
> specified
> Sep 26 05:44:27 a6v systemd[1]: usr-portage.mount mount process exited,
> code=exited status=32
> Sep 26 05:44:27 a6v systemd[1]: Failed to mount /usr/portage.
> Sep 26 05:44:27 a6v systemd[1]: Dependency failed for Remote File Systems.
> Sep 26 05:44:27 a6v systemd[1]: Job remote-fs.target/start failed with
> result 'dependency'.
> Sep 26 05:44:27 a6v systemd[1]: Unit usr-portage.mount entered failed state.
>
>
> # systemctl status remote-fs.target
> remote-fs.target - Remote File Systems
>           Loaded: loaded (/usr/lib64/systemd/system/remote-fs.target;
> enabled)
>           Active: inactive (dead)
>             Docs: man:systemd.special(7)
>
> # grep nfs /etc/fstab
> a6:/usr/portage         /usr/portage    nfs             rw,auto         0 0
> (BTW, this works correctly when booting with openrc.)
>
> Any hints would be much appreciated, thanks.

I believe you have your answer:

> Sep 26 05:44:27 a6v mount[1655]: mount.nfs: rpc.statd is not running but is
> required for remote locking.
> Sep 26 05:44:27 a6v mount[1655]: mount.nfs: Either use '-o nolock' to keep
> locks local, or start statd.

Put nolock in the mount options in fstab (rw,auto,nolock), or get
rpc.statd running. For the later, you will need the service file for
it: a quick googling turned out:

http://en.gentoo-wiki.com/wiki/Systemd#NFS

Put the necessary service files in /etc/systemd/system, make a link to
them in /etc/systemd/system/remote-fs.target.wants (you need to do
this by hand, since they don't seem to have an [Install] section), and
then do a 'systemctl --system daemon-reload'. Afterwards, you should
be able to mount your NFS partition with 'systemctl start
usr-portage.mount'.

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

Reply via email to