21 Sep
2019
21 Sep
'19
8:35 p.m.
Hi All, I have been experimenting with dnfs with nfs-ganesha. It works fine with NFSv3 but not v4. I noticed 2 issues with v4. 1. SetClientID fails as TAG sent by dnfs is not a valid utf8 string. NFS-ganesha is returning NFS4ERR_INVAL in this case. However, nfs-ganesha is using the converted string just for logging. If we skip this check dnfs can proceed further. 2. If length of file handle is not a multiple 4 then dnfs fails. In case of NFSv3 file handles are explicitly padded to make them multiples of 4. Can we do the same for NFSv4. --Satish