[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#809392: marked as done (showmount not showing IPv6 clients)



Your message dated Sat, 14 Sep 2024 10:00:04 +0200 (CEST)
with message-id <20240914080004.94D2CBE2DE0@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #809392,
regarding showmount not showing IPv6 clients
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 owner@bugs.debian.org
immediately.)


-- 
809392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809392
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.2.8-9
Severity: normal

Dear Maintainer,

showmount does not show IPv6 clients.

Steps to reproduce:

1.) umount an NFS share on a client
2.) run "exportfs -f ; exportfs -a" to flush and re-read the kernel
    export table on the server
3.) mount an NFS share on a client
4.) invoke "showmount" or "showmount -a" on the server -> no clients are listed

I tried different showmount invocations (being done on the NFS server
itself):

# showmount 
Hosts on servername:
-> no further output

# showmount -a
All mount points on servername:
-> no further output

# showmount -a localhost
All mount points on localhost:
-> no further output

# showmount localhost
Hosts on localhost:
-> no further output

In the kernel export table, the clients with mounted shares are properly
listed:

# wc -l /proc/fs/nfsd/exports
27 /proc/fs/nfsd/exports

One example:

# grep "::166/128" /proc/fs/nfsd/exports
/s2/sw	fd40:9dc7:b528:8::/64,fd40:9dc7:b528:8::166/128(rw,no_root_squash,sync,wdelay,uuid=8d45a057:f2b448b9:8c3d26e7:f3a00e68,sec=1)

At least from the kernel side everything is fine and the issue seems
somewhere within the nfs-common package.

-- 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
    100024    1   udp  57671  status
    100024    1   tcp  41467  status
    100011    1   udp    948  rquotad
    100011    2   udp    948  rquotad
    100011    1   tcp    948  rquotad
    100011    2   tcp    948  rquotad
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    2   tcp   2049
    100227    3   tcp   2049
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100227    2   udp   2049
    100227    3   udp   2049
    100021    1   udp  57659  nlockmgr
    100021    3   udp  57659  nlockmgr
    100021    4   udp  57659  nlockmgr
    100021    1   tcp  33764  nlockmgr
    100021    3   tcp  33764  nlockmgr
    100021    4   tcp  33764  nlockmgr
    100005    1   udp  33773  mountd
    100005    1   tcp  53433  mountd
    100005    2   udp  33580  mountd
    100005    2   tcp  53509  mountd
    100005    3   udp  41063  mountd
    100005    3   tcp  45829  mountd
-- /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: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=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.113+nmu3
ii  initscripts         2.88dsf-59
ii  libc6               2.19-18+deb8u1
ii  libcap2             1:2.24-8
ii  libcomerr2          1.42.12-1.1
ii  libdevmapper1.02.1  2:1.02.90-2.2
ii  libevent-2.0-5      2.0.21-stable-2
ii  libgssapi-krb5-2    1.12.1+dfsg-19+deb8u1
ii  libk5crypto3        1.12.1+dfsg-19+deb8u1
ii  libkeyutils1        1.5.9-5+b1
ii  libkrb5-3           1.12.1+dfsg-19+deb8u1
ii  libmount1           2.25.2-6
ii  libnfsidmap2        0.25-5
ii  libtirpc1           0.2.5-1
ii  libwrap0            7.6.q-25
ii  lsb-base            4.1+Debian13+nmu1
ii  rpcbind             0.2.1-6+deb8u1
ii  ucf                 3.0030

Versions of packages nfs-common recommends:
ii  python  2.7.9-1

Versions of packages nfs-common suggests:
pn  open-iscsi  <none>
pn  watchdog    <none>

Versions of packages nfs-kernel-server depends on:
ii  libblkid1     2.25.2-6
ii  libc6         2.19-18+deb8u1
ii  libcap2       1:2.24-8
ii  libsqlite3-0  3.8.7.1-1+deb8u1
ii  libtirpc1     0.2.5-1
ii  libwrap0      7.6.q-25
ii  lsb-base      4.1+Debian13+nmu1
ii  ucf           3.0030

-- 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 ---

Reply to: