On 12/10/25 11:36 AM, pgnd wrote:
That's very old information - the default NFS version was changed to v4
with Fedora 13 in 2010.
https://fedoraproject.org/wiki/Features/NFSv4Default
i'm fairly sure that i stumbled on the _need_ to change my setups more recently
than 2010. but, i won't bet on it - time flies :-/
with specified type and netdev, all's good here.
and i'm at a loss as to why type = nfs mounts, vs = nfs4, here fail to mount --
or report as mounted -- my nfs4 shares.
_may_ have to do with the shares NOT all being fedora boxes; that's just a
guess.
It seems that my problem is because I also have bridging set up on this
machine. Apparently the network appears ready way too early.
I posed the question to ChatGPT, and settled on making the NFS mounts be
"noauto", and then creating a service to wait for the network to truly be up
before mounting the filesystem. This works well for me, and I've attached the service
file in case it benefits anyone else.
Thanks for the replies!
Steve
[Unit]
Description=Mount all NFS client filesystems once NAS is reachable
After=network-online.target NetworkManager-wait-online.service
Wants=network-online.target NetworkManager-wait-online.service
[Service]
Type=oneshot
# Wait until the NAS actually responds to ping (up to ~30s)
ExecStartPre=/usr/bin/bash -c 'for i in {1..30}; do ping -c1 -W1 nas >/dev/null 2>&1 && exit 0; sleep 1; done; exit 1'
# Now mount each share explicitly; "noauto" does NOT block these
ExecStart=/usr/bin/mount /shared
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
