Page MenuHomeFreeBSD

update the NFSv4.1/4.2 server's console message indicating that there is no session
ClosedPublic

Authored by rmacklem on Aug 28 2022, 12:09 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Jun 6, 12:33 PM
Unknown Object (File)
Thu, Jun 6, 12:33 PM
Unknown Object (File)
Thu, Jun 6, 12:33 PM
Unknown Object (File)
Tue, Jun 4, 9:42 PM
Unknown Object (File)
Apr 5 2024, 3:03 PM
Unknown Object (File)
Apr 5 2024, 3:03 PM
Unknown Object (File)
Apr 5 2024, 3:03 PM
Unknown Object (File)
Apr 5 2024, 2:50 PM
Subscribers

Details

Summary

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. 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 changes the console message to suggest that the
client's /etc/hostid needs to be checked for uniqueness.

The review is simply for the wording of this new console message.

Test Plan

A NFSv4.1/4.2 server was modified to throw away the session once
every 100000 RPCs and reply NFSERR_BADSESSION. This was done
primarily to test fixes in the FreeBSD client for this case, but the
message is generated when it happens.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable