Re: automount in fedora 17 SOLVED

[paul van der meij <phjvdmeij@xxxxxxxxx>]

The problem was that the firewall on my FC14 fileserver had port 111 (sunrpc) blocked.

The mount on my FC17 client does not use sunrpc, but the automount does.

After allowing port 111 everything worked fine, with everything default in the autofs control files, so no extra nfs parameters.

paul

2012/7/11 paul van der meij <phjvdmeij@xxxxxxxxx>

That was not entirely correct: in the messages file it says:

  get_nfs_info: host pc4 cost 311 weight 0

  mount(nfs): no hosts available

I googled and found a reference to bugzilla #737541, but I don't understand the "resolved' ..

Paul

2012/7/11 paul van der meij <phjvdmeij@xxxxxxxxx>

I started the automount with the -d option, and saw that the error was in get_nfs_info.

The host it self is reachable and a manual mount works, so it has probably to do with nfs4

I will continue to investigate.

Paul

2012/7/11 Louis Lagendijk <louis@xxxxxxxxxxxxxxxxxxx>

On Tue, 2012-07-10 at 22:52 +0200, paul van der meij wrote:
> thanks for reaction, but noI already tried that, but it has something
> to do with changes in the autofs control files
> since FC14, but I have not figured it out yet
>

Please read the man-pages for systemd.automount
and systemd.mount. See especially the /etc/fstab part in the latter.
Louis

--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org