Frank Filz

What version of Ganesha is this? Also, can you get a tcpdump trace (binary with complete packets) including the request that causes the failure? From the stack backtrace, this is...

Do you have a stack back trace of your crash? The above stack back trace doesn't quite make sense (set_op_context_export_fsal_no_release (exp=0x7f707dac1348, fsal_exp=0x7f707da41000, pds=0x0, discard_refstr=true) at /home/vic/Sources/nfs-ganesha/src/FSAL/commonlib.c:3041 is a call to...

OK, I'm going to continue auditing the get and put of references. Clearly we have some mismatches. There aren't that many, so it should be possible to find this by...

Looks like a good fix, will work in the new year to get that submitted and merged. If someone wants to submit via gerrithub that would be helpful otherwise I...

Did you verify? If so, please close.

OK, yea, that makes sense. Would you be willing to submit a patch? We always welcome new contributors.

524 is ENOTSUPP (rather than the usual ENOTSUP). It seems to be a kernel specific error. Also conversion of NFSERR_NOTSUPP or NFS4ERR_NOTSUPP to ENOTSUPP. Can you provide a tcpdump (binary...

Could you do a binary tcpdump capture and share it, such as: tcpdump -s0 -w /tmp/trace.tpc I'd like to see in all it's glory the GETATTR that's resulting in NFS4ERR_NOTSUPP...

Hmm, it's happening on an ACCESS call. Something odd is going on... Can you run with the following LOG config: ``` LOG { COMPONENTS { FSAL=FULL_DEBUG; } } ``` But...

So the Ganesha log timestamps line up with the system clock and the Gluster ones are 2 hours off? There must be a configuration somewhere that is telling Gluster a...