Hi all,
We are testing NFSv4 referral for Linux CentOS 7 with nfs-ganesha and are
running
into some serious issues.
Although, we were able to set up NFSv4 referral using the native Ganesha
FSAL,
we could not get it fully functional for all Linux client system calls.
Basically, the NFSv4 spec suggests to return a NFS4ERR_MOVED on a
LOOKUP done for a remote export. However, this breaks the `stat` system
call on
Linux CentOS 7 (stat’ results in a LOOKUP,GETFH,GETATTR compound). An easy
way to
reproduce the broken behavior is:
1) mount the root of the pseudo file system and
2) issue a `stat` command on the remote export.
The stat returned are corrupt.
After digging into the CentOS 7 client code, we realized that the stat
operation
is never expected to follow the referral. However, switching to returning
NFS4_OK
for stat, then breaks `cd` or a `ls -l` command, because now we don't know
when
to follow the referral.
Does anyone have a successful experience in setting up the NFSv4 referrals
that
they could share? Or, if some suggestions on what we might be doing wrong?
Thanks
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel