Date: Thu, 22 Dec 2022 17:36:23 GMT From: Rick Macklem <rmacklem@FreeBSD.org> To: src-committers@FreeBSD.org, dev-commits-src-all@FreeBSD.org, dev-commits-src-main@FreeBSD.org Subject: git: 6032cf3d6fb5 - main - nfscl: Improve the console message for NFSERR_NOFILEHANDLE Message-ID: <202212221736.2BMHaN6I039270@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by rmacklem: URL: https://cgit.FreeBSD.org/src/commit/?id=6032cf3d6fb5d2e81ff463400bc0c6c8e00b3c3f commit 6032cf3d6fb5d2e81ff463400bc0c6c8e00b3c3f Author: Rick Macklem <rmacklem@FreeBSD.org> AuthorDate: 2022-12-22 17:35:15 +0000 Commit: Rick Macklem <rmacklem@FreeBSD.org> CommitDate: 2022-12-22 17:35:15 +0000 nfscl: Improve the console message for NFSERR_NOFILEHANDLE Since a NFSERR_NOFILEHANDLE reply from an NFSv4 server usually means that the file system is not exported on the server, change the console log message to indicate that. MFC after: 1 week --- sys/fs/nfsclient/nfs_clport.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c index f5d7c3caea0f..53b4c58734c2 100644 --- a/sys/fs/nfsclient/nfs_clport.c +++ b/sys/fs/nfsclient/nfs_clport.c @@ -1179,7 +1179,6 @@ nfscl_maperr(struct thread *td, int error, uid_t uid, gid_t gid) case NFSERR_FHEXPIRED: case NFSERR_RESOURCE: case NFSERR_MOVED: - case NFSERR_NOFILEHANDLE: case NFSERR_MINORVERMISMATCH: case NFSERR_OLDSTATEID: case NFSERR_BADSEQID: @@ -1190,6 +1189,10 @@ nfscl_maperr(struct thread *td, int error, uid_t uid, gid_t gid) printf("nfsv4 client/server protocol prob err=%d\n", error); return (EIO); + case NFSERR_NOFILEHANDLE: + printf("nfsv4 no file handle: usually means the file " + "system is not exported on the NFSv4 server\n"); + return (EIO); default: tprintf(p, LOG_INFO, "nfsv4 err=%d\n", error); return (EIO);
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202212221736.2BMHaN6I039270>