The clientid seemed to be the same in the messages, so I don't think that's directly the issue. Unless that refreshing the clientid causes the client to change its lock owner strings. Frank
-----Original Message----- From: pragash2here@gmail.com [mailto:pragash2here@gmail.com] Sent: Thursday, May 9, 2024 12:29 PM To: support@lists.nfs-ganesha.org Subject: [NFS-Ganesha-Support] Re: lock issue for same clientid on the same node using NFS Ganesha 3.5
Thanks Frank. It is very hard to reproduce. But will keep trying. Do you recommend a log level to turn on ? This is a production environment.
We do notice that on the Ganesha side, there are multiple SETCLIENTIDs in a short period of time with the same opaque string over the same TCP connection. Wondering if this is fine.
The opaque string is
77:Linux NFSv4.0 worker007.acmelab.local/240b:c0e0:205:5500:b464:2:0:b57d _______________________________________________ Support mailing list -- support@lists.nfs-ganesha.org To unsubscribe send an email to support-leave@lists.nfs-ganesha.org