This post is more than 5 years old
9 Posts
0
1064
April 3rd, 2017 01:00
Mounting NFS4 with shortname
Hi,
So trying to get NFSv4 export mounted on a customers Linux client but having no luck as such in terms of how the customer wishes to mount the export.
VNX config:
server_export Customer_VDM -P nfs -name ncdv -option nfsv4only /nonprod/ncdv
[user@VNX044-CS0 ~]$ server_export Customer_VDM
Customer_VDM :
export "/nonprod/ncdv" name="/ncdv" nfsv4only
The directory structure has a mountpoint called nonprod mounted on a filesystem of the same name. No export for the root.
We create a mountpoint called ncdv as per the above and export it assuming the customer can mount it as /ncdv as we set the name.
[root@chrisnfs mnt]# showmount -e 100.64.17.193
Export list for 100.64.17.193:
/nonprod/ncdv (everyone)
/ncdv (everyone)
When we use nfsv3 we can specify mount vnx:/ncdv /mnt/nfs or mount vnx:/nonprod/ncdv /mnt/nfs and both work.
When we use nfsv4 we can only mount using vnx:/nonprod/ncdv as it gives an error stating the file or directory doesn't existing when specifying mount vnx:/ncdv
Any ideas on what i need to do either on the client or vnx side?
ChrisFranklin2
9 Posts
0
April 9th, 2017 22:00
FYI i logged a ticket with EMC and their response was as follows:
Greetings.
Please be informed that i've taken ownership of this case,
Thank you for providing a detail desription of the issue, from what I understand it appears that you might be trying to mount the NFSv4 export usng alias name on Linux client. There's a limitation with linux client as mentioned in KB: 378262 that has been attached to this email for your reference.
In short, when we execute this command "server_export Customer_VDM -P nfs -name ncdv -option nfsv4only /nonprod/ncdv", a symblic link is created
/ncdv ---> /nonprod/ncdv
In NFSv3, we can mount symbolic links but in NFSv4, it doesnt work for Linux Client. In NFSv4, there is a mount protocol where the symbolic link cannot be presented as a directory. This is working as designed and there's no solution possible at the Storage side. Additionally, issues only seem to be restricted with Linux machines, as it's confirmed that Solaris running on code higher than 11 doesnt encounter this isssue.
Workaround:
- Use the full path to mount the export for the Linux Client.
- Possibly work with Linux vendor to pursue a solution.