Your message dated Fri, 13 Mar 2026 18:40:40 +0000
with message-id <[email protected]>
and subject line Bug#1130346: fixed in nfs-utils 1:2.8.7-1
has caused the Debian Bug report #1130346,
regarding nfs-common: nfsrahead crashes when invoked by udev, creating many
“.NNNNN” files on root
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.)
--
1130346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1130346
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nfs-common
Version: 1:2.8.6-1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
When nfs-common is installed on Debian, udev invokes
/usr/libexec/nfsrahead via
/usr/lib/udev/rules.d/99-nfs.rules. On boot nfsrahead fails with an I/O
error
and repeatedly logs "expected the device number of a BDI; is udev ok?", and
numerous files named "." (about 20) are created in the root filesystem,
consuming storage.
Steps to reproduce:
- Install nfs-common on Debian (current unstable).
- Reboot the system.
- Observe repeated journal/syslog messages from udev and nfsrahead and
multiple
files named ".NNNNN" in /.
Observed behavior:
- Journal shows repeated lines like: (udev-worker)[PID]:
/usr/lib/udev/rules.d/99-nfs.rules:1 PROGRAM="/usr/libexec/nfsrahead %k":
Failed to execute "/usr/libexec/nfsrahead ": Input/output error
nfsrahead[PID]:
expected the device number of a BDI; is udev ok?
- Many files with names matching the regex /^\.\d+$/ are created in the root
directory (/) during boot.
- Manually running /usr/libexec/nfsrahead from a console does not
reproduce the
crash.
Additional information:
- package: nfs-common
- affected binary: /usr/libexec/nfsrahead
- riggering rule: /usr/lib/udev/rules.d/99-nfs.rules
(PROGRAM="/usr/libexec/nfsrahead %k")
- Relevant log snippets: "(udev-worker)[...]:
PROGRAM="/usr/libexec/nfsrahead
%k": Failed to execute "/usr/libexec/nfsrahead ...": Input/output error
nfsrahead[...]: expected the device number of a BDI; is udev ok?"
-- 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=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/nfs.conf --
[general]
pipefs-directory=/run/rpc_pipefs
[nfsrahead]
[exports]
[exportfs]
[gssd]
[lockd]
[exportd]
[mountd]
manage-gids=y
[nfsdcld]
[nfsd]
[statd]
[sm-notify]
[svcgssd]
-- /etc/nfs.conf.d/*.conf --
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.19.6+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages nfs-common depends on:
ii adduser 3.154
ii keyutils 1.6.3-6+b1
ii libc6 2.42-13
ii libcap2 1:2.75-10+b9
ii libcom-err2 1.47.4-1
ii libevent-core-2.1-7t64 2.1.12-stable-10+b2
ii libgssapi-krb5-2 1.22.1-2
ii libk5crypto3 1.22.1-2
ii libkeyutils1 1.6.3-6+b1
ii libkrb5-3 1.22.1-2
ii libmount1 2.41.3-4
ii libnfsidmap1 1:2.8.6-1
ii libtirpc3t64 1.3.6+ds-1
ii libwrap0 7.6.q-36+b2
ii rpcbind 1.2.7-1
ii ucf 3.0052
Versions of packages nfs-common recommends:
ii python3 3.13.9-3
Versions of packages nfs-common suggests:
pn open-iscsi <none>
pn watchdog <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nfs-utils
Source-Version: 1:2.8.7-1
Done: Salvatore Bonaccorso <[email protected]>
We believe that the bug you reported is fixed in the latest version of
nfs-utils, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Salvatore Bonaccorso <[email protected]> (supplier of updated nfs-utils package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 13 Mar 2026 17:48:49 +0100
Source: nfs-utils
Architecture: source
Version: 1:2.8.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team <[email protected]>
Changed-By: Salvatore Bonaccorso <[email protected]>
Closes: 1130346
Changes:
nfs-utils (1:2.8.7-1) unstable; urgency=medium
.
* New upstream version 2.8.7
- nfsrahead: zero-initialise device_info struct (Closes: #1130346)
Checksums-Sha1:
d3b32d4cc3a5966ddd6b8b4669f4e131c9809d89 2659 nfs-utils_2.8.7-1.dsc
996bfb41b12058087287415ff987ea96b5edcfea 755520 nfs-utils_2.8.7.orig.tar.xz
3f78f563a6de1d4963b9cda18aba538306467c21 50196 nfs-utils_2.8.7-1.debian.tar.xz
Checksums-Sha256:
35496493acfce6d0ea6b0d01882821b5dd0086fea14bb34e8bc61115d0760e3b 2659
nfs-utils_2.8.7-1.dsc
59d0f1e17b18efaa60ea3ccf89a9cad3217f8d3b23c18d2fe34b25c8969d60ae 755520
nfs-utils_2.8.7.orig.tar.xz
5cbbd50ecde59374431e1d716addb21d64e0acdfa9c5f970246114b14c320edf 50196
nfs-utils_2.8.7-1.debian.tar.xz
Files:
4f1b4f75589eb5aeba2afac7740d1887 2659 net optional nfs-utils_2.8.7-1.dsc
69a6ab83132f4a82134e925ac4c7f8c8 755520 net optional
nfs-utils_2.8.7.orig.tar.xz
a0f8c7810c4b878a713077e6efbb83b5 50196 net optional
nfs-utils_2.8.7-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmm0V2xfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EL+gQAIyGMQjLJUd5+cPk0wViSpBWndi2Qabb
TJcPD5Rdsy5ArpwU244Z6HLa/JH2T5ADLS7GAkvOs9DNZfvjUob/V/bt97cxxoX2
tVrZW8IACaa5PyuBCLdWa2s+PGs9h9F5vx6V8fALRXIidePriNQ7idPfvFmfptFG
NxEBTgOoObExcG9eNvaGynqADfoUm8r/1OLwFn0C+N84jwzKaxXdoilK72P1FlHf
QHT1QMgP+WFOgS1UH3Y8j2rEpxfbzrFDmsxkS1x40ZEFYZq1PPDUzqADKRp0bhnk
a9Q0KPk0fqxtiHslcsv1l82iLHUbfGQNXOqainevwwdNB42tlKTFua6XnCJjWB5H
1oM8sfe8DjqPAv7sYgKjbTqRT/T00drkNP6FsBSBpQovEEjyq1iBq1kab/Q6e/SZ
EXh48FQp0vqOyWoU3SHTodrorQyqNzqV1vy6vprmiykDT2OkqqW3Sf6nxjm/XlGD
jnUqqjuxy9jRi8eDoHA3VSMdEeB1oqAgdSlL3mULhSNogqLwcKscziT11aMHdqsw
Lt4dydC1KfgwFIgBNmdrrFOH+wPv8x6fleB3WnHUFPQkBqPNvdjlzyMLVW3ZhKfl
ZY2GQg+BFbRYogvv2twC3onmrehs3xucNqdHW35fOIY4UpnOTOjDrdeRdI6Mx/uC
UMScsR5+PG28
=szVY
-----END PGP SIGNATURE-----
pgpMqBUD_ashh.pgp
Description: PGP signature
--- End Message ---
