Skip to content

No /etc/protocols or /etc/services: NFSv3 mounts fail with 'Protocol not supported' #316

Closed

Description

@jeefy

Summary

Bluefin Server ships /etc/netconfig and /etc/rpc (from libtirpc) but no /etc/protocols and no /etc/services. Anything that calls getprotobyname() / getservbyname() fails, which today breaks NFSv3 mounts even though nfs-utils (#295) is in the image and NFSv4 works.

Reproduction (26.09.758, kubeadm worker, diskless BIOS)

# getent protocols tcp; echo rc=$?
rc=2
# getent services sunrpc; echo rc=$?
rc=2
# ls /etc/protocols /etc/services
ls: cannot access '/etc/protocols': No such file or directory
ls: cannot access '/etc/services': No such file or directory

# mount -t nfs -o ro,vers=3 <nfs-server>:/storage/<share> /mnt
mount.nfs: Protocol not supported
# mount -t nfs -o ro,vers=3,proto=tcp,mountproto=tcp -v <nfs-server>:/storage/<share> /mnt
mount.nfs: Failed to find 'tcp' protocol

Same share, same server, -o vers=3 from a Flatcar node succeeds (vers=3,mountvers=3,mountproto=udp), so the server is fine. On the Bluefin node rpcbind.socket is active and rpcinfo -p 127.0.0.1 lists portmapper + status, so rpcbind/statd themselves work; libtirpc simply cannot build the mountd/portmapper client without protocol/service names. rpcinfo -p <remote-ip> also fails with RPC: Unknown host for the same reason.

NFSv4 (vers=4.1) mounts fine because it needs neither.

Expected

/etc/protocols and /etc/services present in the image, as on every general-purpose distro (Fedora setup, Debian netbase, Arch/Gentoo iana-etc, Flatcar ships them via glibc/baselayout). freedesktop-sdk has no element for them as far as I can see; a small project-local element that installs the two files from iana-etc (https://github.com/Mic92/iana-etc releases, MIT) into %{sysconfdir} should do — they are plain text, ~800 KB together. hosts.bst and nsswitch-config.bst in os-base.bst are the obvious neighbours.

Impact

  • NFSv3 clients (older NAS boxes, some CSI drivers that pin nfsvers=3) cannot mount.
  • Any tool using service names (telnet host ssh, nc host http, iptables -p tcp --dport ssh, Python socket.getservbyname) fails with "unknown service" / "protocol not supported".

Found while verifying #294 / #295 on a real cluster.

Activity

  1. added
    hive/covered-by-prHive verified that an open PR references or claims this issue; still actionable until confirmed
    on Sep 30, 2026
  2. added
    hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmation
    and removed
    hive/covered-by-prHive verified that an open PR references or claims this issue; still actionable until confirmed
    on Sep 30, 2026
  3. added a commit that references this issue on Sep 30, 2026
    d82b3bc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions