Your message dated Sat, 14 Sep 2024 09:31:48 +0200 (CEST) with message-id <[email protected]> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #883890, regarding nfs-common: Fully Qualified DNS Name mounts in fstab fail to be mounted to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 883890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883890 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: nfs-common Version: 1:1.3.4-2.1 Severity: grave Justification: renders package unusable File systems correctly mounted after "reached target network online" File systema rw in both cases. Case 1 1. I deleted resolv.conf 2. Root fs rw in fstab 3. File systems mounted by IP address 4. resolve.conf built by end of boot when login possible proc /proc proc defaults 0 0 /dev/mmcblk0p1 /boot vfat defaults,ro 0 2 #PARTUUID=62bc0a1f-02 / ext4 defaults,noatime 0 1 192.168.1.10:/nfsroot/r.32.test / nfs defaults,rw 0 0 192.168.1.10:/nfsroot/b827eb/c23849/var /var nfs defaults,rw 0 0 192.168.1.10:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0 #browne.danum.local:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0 tmpfs /tmp tmpfs nodev,nosuid,size=1%,mode=1777 0 0 Case 2 1. I deleted resolv.conf 2. Root fs rw in fstab 3. File systems mounted by server name 4. Mount failed. proc /proc proc defaults 0 0 /dev/mmcblk0p1 /boot vfat defaults,ro 0 2 #PARTUUID=62bc0a1f-02 / ext4 defaults,noatime 0 1 192.168.1.10:/nfsroot/r.32.test / nfs defaults,rw 0 0 192.168.1.10:/nfsroot/b827eb/c23849/var /var nfs defaults,rw 0 0 #192.168.1.10:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0 browne.danum.local:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0 tmpfs /tmp tmpfs nodev,nosuid,size=1%,mode=1777 0 0 Case 2 1. resolv.conf not deleted. 2. Root fs rw in fstab 3. File systems mounted by server name 4. Mount failed. proc /proc proc defaults 0 0 /dev/mmcblk0p1 /boot vfat defaults,ro 0 2 #PARTUUID=62bc0a1f-02 / ext4 defaults,noatime 0 1 192.168.1.10:/nfsroot/r.32.test / nfs defaults,rw 0 0 192.168.1.10:/nfsroot/b827eb/c23849/var /var nfs defaults,rw 0 0 #192.168.1.10:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0 browne.danum.local:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0 tmpfs /tmp tmpfs nodev,nosuid,size=1%,mode=1777 0 0 Conclusion: name resolution, dns lookup, is not performed at fstbab mount time. This is supposed to work. Who's issue is this? systemd or mount? -- Package-specific info: -- rpcinfo -- -- System Information: Distributor ID: Raspbian Description: Raspbian GNU/Linux 9.1 (stretch) Release: 9.1 Codename: stretch Architecture: armv7l Kernel: Linux 4.9.59-v7+ (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nfs-common depends on: ii adduser 3.115 ii init-system-helpers 1.48 ii keyutils 1.5.9-9 ii libc6 2.24-11+deb9u1 ii libcap2 1:2.25-1 ii libcomerr2 1.43.4-2 ii libdevmapper1.02.1 2:1.02.137-2 ii libevent-2.0-5 2.0.21-stable-3 ii libgssapi-krb5-2 1.15-1+deb9u1 ii libk5crypto3 1.15-1+deb9u1 ii libkeyutils1 1.5.9-9 ii libkrb5-3 1.15-1+deb9u1 ii libmount1 2.29.2-1 ii libnfsidmap2 0.25-5.1 ii libtirpc1 0.2.5-1.2 ii libwrap0 7.6.q-26 ii lsb-base 9.20161125+rpi1 ii rpcbind 0.2.3-0.6 ii ucf 3.0036 Versions of packages nfs-common recommends: ii python 2.7.13-2 Versions of packages nfs-common suggests: pn open-iscsi <none> pn watchdog <none> -- no debconf information
--- End Message ---
--- Begin Message ---Hi [This reply and bug closer is sent for doing BTS maintenance for src:nfs-utils bugs] This bug was reported against a very old nfs-utils version without much followups/triaging itself. If you can reproduce it with the current version in unstable/testing or stable at least, please reopen the bug, https://www.debian.org/Bugs/server-control for details. Regards, Salvatore
--- End Message ---
