aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRick Macklem <rmacklem@FreeBSD.org>2022-08-28 01:31:20 +0000
committerRick Macklem <rmacklem@FreeBSD.org>2022-08-28 01:31:20 +0000
commitb875d4f5ddcbe0ce06f22650dd471b7518546dd6 (patch)
treec3deb7d06d9c080afd825017e7d8454a16266a86
parentfb29f817586972444d65b1548287a51f27891639 (diff)
downloadsrc-b875d4f5ddcb.tar.gz
src-b875d4f5ddcb.zip
nfsd: Update console message for no session found
The NFSv4.1/4.2 server generates a console message that indicates that there is no session. I was until recently perplexed w.r.t. how this could occur. It turns out that the common cause is multiple NFS clients with the same /etc/hostid. The host uuid is used by the FreeBSD NFSv4.1/4.2 client as a unique identifier for the client. If multiple clients use the same host uuid, this indicates to the NFSv4.1/4.2 server that they are the same client and confusion occurs. This trivial patch modifies the console message to suggest that the client's /etc/hostid needs to be checked for uniqueness. Reviewed by: asomers MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D36377
-rw-r--r--sys/fs/nfsserver/nfs_nfsdstate.c7
1 files changed, 5 insertions, 2 deletions
diff --git a/sys/fs/nfsserver/nfs_nfsdstate.c b/sys/fs/nfsserver/nfs_nfsdstate.c
index aac845e68af7..d5d7f9fbd363 100644
--- a/sys/fs/nfsserver/nfs_nfsdstate.c
+++ b/sys/fs/nfsserver/nfs_nfsdstate.c
@@ -6383,9 +6383,12 @@ nfsrv_cache_session(struct nfsrv_descript *nd, struct mbuf **m)
}
if (cp != NULL)
printf("nfsrv_cache_session: no session "
- "IPaddr=%s\n", cp);
+ "IPaddr=%s, check NFS clients for unique "
+ "/etc/hostid's\n", cp);
else
- printf("nfsrv_cache_session: no session\n");
+ printf("nfsrv_cache_session: no session, "
+ "check NFS clients for unique "
+ "/etc/hostid's\n");
free(buf, M_TEMP);
}
m_freem(*m);