On Wed, 26 Apr 2023, 17:55:09 +0200, Larry Finger wrote:
On 4/26/23 10:04, Bruce Ferrell wrote:
On 4/26/23 3:44 AM, Manfred Hollstein wrote:
Hi there,
On Tue, 25 Apr 2023, 18:00:48 +0200, Dominique Leuenberger wrote:
[...] ==== nfs-utils ==== Subpackages: libnfsidmap1 nfs-client nfs-kernel-server
- Update to version 2.6.3 - https://kernel.org/pub/linux/utils/nfs-utils/2.6.3/2.6.3-Changelog - Remove patches from this release: - 0006-nfsd-allow-server-scope-to-be-set-with-config-or-com.patch - 0007-mount.nfs-always-include-mountpoint-or-spec-if-error.patch - 0008-nfsd.man-fix-typo-in-section-on-scope.patch - Remove systemd/50-nfs.conf (was removed in upstream in d8d29f85) and the realted patch (bsc#1200710). 0005-modprobe-avoid-error-messages-if-sbin-sysctl-fail.patch. - New file /usr/lib/udev/rules.d/60-nfs.rules (which replaced in upstream systemd/50-nfs.conf in 9466df03). - Add fsidd: - /usr/lib/systemd/system/fsidd.service - /usr/lib/udev/rules.d/60-nfs.rules - /usr/sbin/fsidd does NFS still work for anybody with this update? I used to be able to export various directories on several hosts and automount them via autofs. With this update any attempt to talk to the server hangs the client.
TIA, cheers.
l8er manfred
Manfred
The first question I'd ask is does the NFS export/mount work manually? I pose question this because autofs has long been somewhat problematic even when NFS is working fine.
It is really strange... My NFS configuration evolved over years, and I have changes to /etc/nfs.conf.local, /etc/nfsmount.conf and /etc/sysconfig/nfs. I just disabled nfs-server.service and autofs.service from auto-starting, then rebooted the system. I tried Jan's very small test and failed, of course. I played with some parameters in /etc/exports (e.g. changing my local network address into *), but that did not help. Funnily *sometimes* mounting with "-o nfsvers=3" works, but only *sometimes*. My /etc/exports contains the following entries: /.e/ 192.168.17.0/24(rw,no_root_squash,async,no_subtree_check,fsid=0,crossmnt) /.e/home 192.168.17.0/24(rw,no_root_squash,async,no_subtree_check) /.e/var/lib/samba/shares 192.168.17.0/24(rw,no_root_squash,async,no_subtree_check) where /.e is a symbolic link to / - moving to NFSv4 I found no other way to export my root file system. When the same mount, which worked once, is tried again (after having umounted it before, of course), I sometimes see the following in the journal: rpc.mountd[6311]: authenticated mount request from 192.168.17.11:882 for /home (/home) but the mount hangs and nothing is actually mounted.
I have two Tumbleweed desktops that export filesystems with NFS to my laptop. All systems are fully updated, and NFS is working exactly the way I expect.
Are you using NFSv4 or v3?
I do have manual exports without autofs.
Larry
Worried... Cheers. l8er manfred