11:40 a.m.
Any guesses as to what can lead to such an improper tear-down, or how to
diagnose this further? Is there anything that I should look for in either
nfs-ganesha server or nfs client logs that would give any indication of
such an improper tear-down.
I can tell you that, almost invariably, I am restarting nfs-ganesha via
either:
systemctl restart nfs-ganesha
or
systemctl stop nfs-ganesha
systemctl start nfs-ganesha
so I don't know what else I could do to improve the tear-down.
Thanks,
Todd
On Thu, 9 Apr 2020, Daniel Gryniewicz wrote:
> 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(a)lists.nfs-ganesha.org
>> To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org
>
>