Package: klibc-utils
Version: 2.0.6-1+deb10u1
Severity: critical
File: nfs
Justification: breaks the whole system
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Distributor ID: Bunsenlabs
Description:BunsenLabs GNU/Linux 10.5 (Lithium)
Release:10.5
Codename: buster
Architecture: x86_64
Kernel: Linux 5.10.0-0.deb10.16-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages klibc-utils depends on:
ii libklibc 2.0.6-1+deb10u1
klibc-utils recommends no packages.
klibc-utils suggests no packages.
-- no debconf information
First some background: I am an experienced software engineer who spend many
years in the software
industry, mostly as a software develeper in the Integrated Circuit
Compter-Aided Design industry.
I say this to let you know I have a very good background in software.
Second, I filed this as a klibc-utils bug. This is bogus! When entering the
report, I did not see
and way to report the problem as an NFS problem. I may have missed that during
the report process.
My apologies if I did miss it. I repeat, this is an NFS problem.
The problem I have run into is that when installing a new instance of the
Bunsenlabs Lithium release I
have frequently run into the message:
mount.nfs: requested NFS version or transport protocol is not supported
This error comes up despite the fact that I am running the same default version
of nfs on both the
client and on the server.
In the past, I have been able to resolve the issue by restarting the nfs server
on the LAN server.
This does not work now. So far I have spent roughly 10 hours trying to get my
internal network
up and running, and I expect to spend a good part of today getting my network
backup. FYI, I have
internet service on each of my computers, but internally I cannot mount server
file systems on my
clients.
However, even when this fixes the problem, the error message is still a bug!
Why do I say this?
This is true, because in recent years, I have been using NFS, version 3, and
nothing else.
The error message itself is wrong. If nothing else, the software can be
improved by reporting
which version of nfs is found on the server and which version is found on the
client. My
expectation is that the error detecting message will then reveal that the
versions are NOT
incompatible. So please, provide the additional information. I will then
consider this problem
fixed. My expectation is that you will then receive reports from myself and
others that we
are receiving the message despite the fact that the nfs versions are identical.
I would not be surprised if the error a result of fact that the client and
server have
different versions of one or more library files. This is only speculation.
My email was given as jjanderson52...@gmail.com. This is a valid email address.
Just to let you
know I do not look at it everyday, but I will try to check regularly so that I
can provide
additional information if you may need it.
Whoever receives this message, I would appreciate that you acknowledge that you
are looking
into the problem. Thank you for taking the time!
Regards,
Jim Anderson
