Unsolved
This post is more than 5 years old
3 Apprentice
•
318 Posts
0
867
November 27th, 2014 02:00
symlink on cs
Hi,
To minimize impact on NFS clients, it was necessary to create symlinks so a new structure of fs exports from Celerra mapped to the old system, Now we have migrated the fs on the celerra, so its necesssary to update the symlinks. I know somewhere it is possible to get a r/w view on the cs so I can accomplish this, but for the life of me I cannot remember how, does anyone know how to do this ?
No Events found!
Jyothi_P_Bharat
317 Posts
1
December 4th, 2014 23:00
Hi,
Are you looking for this:
# server_param server_3 -facility shadow -info followabsolutpath -v
server_3 :
name = followabsolutpath
facility_name = shadow
default_value = 0
current_value = 0
configured_value =
user_action = none
change_effective = immediate
range = (0,3)
description = Whether to follow the absolute path in symlinks
param shadow followabsolutpath=0
_Neither bit 0 or 1 is set and CIFS cannot follow Unix symbolic link paths
param shadow followabsolutpath=1
_=1 means that bit 0 is set & symbolic links are enabled--root-owned absolute path symlinks can be followed by CIFS Users
param shadow followabsolutpath=3
_=3 means that bit 0 & 1 are set, symbolic links are enabled, and CIFS Users can follow any absolute path symlink (See AR84916)
Thanks
Jyothi
Rainer_EMC
4 Operator
•
8.6K Posts
0
December 5th, 2014 06:00
Another way to create symlinks is the little kown NFS aliasing feature – if you use the name option for server_export –P nfs it will actually create a symlink
For example if you use
server_export server_2 -P nfs –name fs_nw_new /root_vdm_5/fs_nw_test
it will create a symlink /fs_nw_new pointing to /root_vdm_5/fs_nw_test in the data mover root
This way clients can mount the NFS share using either path
cadencep45
3 Apprentice
•
318 Posts
0
December 7th, 2014 23:00
Obscure and useful information !