FreeBSD Bugzilla – Attachment 195165 Details for
Bug 226494
ESX NFSv4.1 client fails when ReclaimComplete for one FS fails
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
[patch]
Just return NFS_OK for ReclaimComplete with rca_one_fs TRUE
reclaimcom3.patch (text/plain), 931 bytes, created by
Rick Macklem
on 2018-07-16 00:03:19 UTC
(
hide
)
Description:
Just return NFS_OK for ReclaimComplete with rca_one_fs TRUE
Filename:
MIME Type:
Creator:
Rick Macklem
Created:
2018-07-16 00:03:19 UTC
Size:
931 bytes
patch
obsolete
>--- fs/nfsserver/nfs_nfsdserv.c.noreclaim 2018-07-15 16:48:33.564061000 -0400 >+++ fs/nfsserver/nfs_nfsdserv.c 2018-07-15 16:57:30.362705000 -0400 >@@ -4230,9 +4230,16 @@ nfsrvd_reclaimcomplete(struct nfsrv_desc > goto nfsmout; > } > NFSM_DISSECT(tl, uint32_t *, NFSX_UNSIGNED); >- if (*tl == newnfs_true) >- nd->nd_repstat = NFSERR_NOTSUPP; >- else >+ /* >+ * I believe that a ReclaimComplete with rca_one_fs == TRUE is only >+ * to be used after a file system has been transferred to a different >+ * file server. However, RFC5661 is somewhat vague w.r.t. this and >+ * the ESXi 6.7 client does both a ReclaimComplete with rca_one_fs >+ * == TRUE and one with ReclaimComplete with rca_one_fs == FALSE. >+ * Therefore, just ignore the rca_one_fs == TRUE operation and return >+ * NFS_OK without doing anything. >+ */ >+ if (*tl == newnfs_false) > nd->nd_repstat = nfsrv_checkreclaimcomplete(nd); > nfsmout: > NFSEXITCODE2(error, nd);
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 226494
:
191365
|
195165
|
195222