Your message dated Sat, 14 Sep 2024 09:45:57 +0200 (CEST) with message-id <20240914074557.1afd3be2...@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #855051, regarding nfs-common: wrong shutdown sequence of wifi then nfs leaves nfs mounts hanging 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 ow...@bugs.debian.org immediately.) -- 855051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: nfs-common Version: 1:1.3.4-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I use autofs to mount NFS * What exactly did you do (or not do) that was effective (or ineffective)? I've noticed that when I shutdown, my wifi often goes down before the NFS volume is unmounted. This leads to a hang in the shutdown. I can provide journalctl logs if that would help. * What was the outcome of this action? I usually get frustrated, search the web for work-arounds, and file bug reports. I've found some reports of this issue in various places. I wonder if there is already a debian bug to track this issue or, maybe, a fix is already known? * What outcome did you expect instead? I expected a very rapid shutdown. *** End of the template - remove these template lines *** -- Package-specific info: -- rpcinfo -- program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD= NEED_GSSD= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /run/rpc_pipefs [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages nfs-common depends on: ii adduser 3.115 ii init-system-helpers 1.47 ii keyutils 1.5.9-9 ii libc6 2.24-9 ii libcap2 1:2.25-1 ii libcomerr2 1.43.4-2 ii libdevmapper1.02.1 2:1.02.137-1 ii libevent-2.0-5 2.0.21-stable-2.1 ii libgssapi-krb5-2 1.15-1 ii libk5crypto3 1.15-1 ii libkeyutils1 1.5.9-9 ii libkrb5-3 1.15-1 ii libmount1 2.29.1-1 ii libnfsidmap2 0.25-5.1 ii libtirpc1 0.2.5-1.1 ii libwrap0 7.6.q-26 ii lsb-base 9.20161125 ii rpcbind 0.2.3-0.5 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 ---
