Hi Pradeep, thanks for your response. On 14.05.2018 17:48, Pradeep wrote: > The patch is for NFS client side bug where it was initializing the > attributes to zero if NFS4ERR_MOVED is returned in LOOKUP; but referral > was not followed later. This only happens with NFSv4 server and the > specific error (NFS4ERR_MOVED). > > It is not related to nfs-ganesha - it can be reproduced with kernel NFS > as well. > > Are you seeing any regressions with the patch? I would think so. Since that patch arrived in Kernel 3.16, it would not even try to follow the referral as it did before. When I just revert this specific patch for the kernel, it works. On the referrer server, we use nfs-ganesha 2.4.5-2 with Christoph's patch for nfs referral (https://sources.debian.org/src/nfs-ganesha/2.4.5-2%7Ebpo9+1/debian/patches/nfs-ganesha-nfsrefer.patch). The actual NFS server is a NetApp cluster. I'm not so sure right now if it is not maybe a bug in nfs-ganesha (that maybe even got fixed in the meantime), so I thought, maybe you know. Thanks, Moritz
Attachment:
signature.asc
Description: OpenPGP digital signature