https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261291
--- Comment #17 from Alan Somers <asom...@freebsd.org> --- 1) After nfsrevoke, the server does reply NFS4ERR_ADMIN_REVOKED to the next CREATE_SESSION. Then the client tries a new EXCHANGE_ID, and this time the server replies with a different client_id. The next CREATE_SESSION is successful. 2) With your patch, the server does reply NFS4ERR_SEQ_MISORDERED. 3) However, the ESXi client doesn't treat NFS4ERR_SEQ_MISORDERED any differently. It still gets stuck in an infinite loop until nfsrevoke fixes it. -- You are receiving this mail because: You are the assignee for the bug.
