I have the following configuration on a unified vnx 5600:
nas_version: 8.1.9-211
VDM name: agntssflg01
interface configured & attached to VDM to support NFS exports
new 1GB filesystem created & mounted to vdm as /TSS
export created: agntssflg01:/TSS
What I want to do, is create a new symbolic link in the root filesystem of the VDM named /ABC that has the target of /TSS
normally, on any linux server, for local application/use access, I would do this as: #ln -s /TSS /ABC
Can the same thing be done on a VDM?
My constraints (self imposed & developer imposed) are:
I would prefer to not create multiple filesystems & mount them at the needed paths
I would prefer to not create the export on the physical DM
The developer needs 9-12 exports for testing, with a space need of a few MB (thus creating multiple 1GB minimum size for each export is a waste of space)
All the exports needed on the VDM follow the format of: 'agntssflg01:/<3 letters>'
All the exports need to available (which means i can't remove/re-add the filesystem to each one as needed/scripted)
I have tried to mount the same filesystem again at a different mount point, but that didn't work
That works for creating 1 of the 9-12 exports I need.
I was able to create one(1) additional name and access it remotely, but when I tried creating a 3rd entry for hte name, it overwrote the 2nd one I created.
So last night I was trying to figure out how to get to the root VDM, because if I could get to the root where the exports start from, I can create symbolic links at the root to subfolder in the filesystem & export those.
After reading/googling/looking on the VNX, I figured out that I could mount the DM root filesystem to the control station:
#mount server_2:/ /mnt/vdm20
In there, I could see the folder structure for the VDMs (e.g. root_vdm_##)
Looking into the root_vdm_20 folder (which matches the VDM i needed this on), I found the new filesystem mounted as /TSS
Poking around, in the .etc folder, i found the vdm.cfg file for the exports.
Short version, is I was able to create softlinks to subfolders inside the /TSS mount
#ls -s /root_vdm_20/TSS/
once those were created, I was able to create new exports to the symlink
make sure you test this with NFSv4 as well - if your developer systems use it
P.S.: please to dont change anything in .etc - these arent config files that are meant to be edited - they need to be in sync with other places like NASDB
Rainer_EMC
6 Operator
•
8645 Posts
1227
0
Posted December 6th, 2017 02:00
I would suggest to try the -name option of server_export aka. NFS aliasing
It should do what you want and create a symlink that can be used as an alternate path to the export