[NFS-Ganesha-Devel] Re: O_TRUNC in open2

Hello again, Well, after a cup of coffee I double checked thing. I confirm that for a call open with O_TRUNC flag, my NFS client (linux centos7) sends a OPEN message (do'nt see FSAL_O_TRUNC flag propagated to open2 so may be it is not set by the client) and a separate SETATTR message with size = 0. So I don't know how my FSAL can handle O_TRUNC within open2 function and AWAIU since it does not return the attr changes (size and ctime) in attrs_out, MDcache can not invalidate the cache and I'll have info inconsistency between the backend and the mdcache theorically. Can you advice? Thank you