This error means that Ganesha got NFS4ERR_SEQ_MISORDERED from the remote server. I'm not sure what would cause this in this case, but a guess is that maybe Ganesha is being restarted, and the previous session was not properly torn down? Daniel On 4/9/20 9:34 AM, Todd Pfaff wrote:

I'm using nfs-ganesha 2.8 on CentOS 7.

Inconsistently, I will get errors like this in ganesha.log at nfs-ganesha startup:

  08/04/2020 22:25:26 : epoch 5e8e8796 : ganesha : ganesha.nfsd-1647[main]   init_export_root :EXPORT :CRIT :Lookup failed on path, ExportId=20040   Path=/pool/export/a FSAL_ERROR=(Invalid object type,10063)

This is using PROXY FSAL for a valid, functioning nfs export from another host X.  I have other PROXY exports with different export IDs and different paths for this same host X that succeed during the same startup for which the error above is generated.  I will see different exports IDs and paths in these errors for different startups, so it's not consistently always failing on one particular export ID.

From one startup to another:

- I may see this error about this same export, - I may see this error about some other export, - I may see no errors.

Thoughts?

Thanks, Todd _______________________________________________ Support mailing list -- support@lists.nfs-ganesha.org To unsubscribe send an email to support-leave@lists.nfs-ganesha.org