This post is more than 5 years old
1 Rookie
•
82 Posts
0
8023
August 10th, 2009 08:00
How to share an NFS mount (exported to Unix) to a windows server.
Hi All,
We have a file system exported to a unix server, (mounted on Datamover 4). But its not mounted on a VDM inorder to share it to a windows server.
Could some help me in explaining the correct procedure to share it to a windows server.
Please let me know if you have any questions.
Thank you.
We have a file system exported to a unix server, (mounted on Datamover 4). But its not mounted on a VDM inorder to share it to a windows server.
Could some help me in explaining the correct procedure to share it to a windows server.
Please let me know if you have any questions.
Thank you.
No Events found!


nandas
6 Operator
•
1.5K Posts
0
August 10th, 2009 15:00
So the revised steps will be -
1) Delete any NFS export on the file system /summit
$ server_export server_4 -P nfs -unexport -perm /summit
2) Unmount the file system from server_4
$ server_umount server_4 -perm summit
3) Delete the existing mount point on server_4 for the file system (which will be mounted on a new path so this is a cleaning process to delete unused mountpoint)
$ server_mountpoint server_4 -delete /summit
4) Create a new Mount Point for the file system to be mounted on VDM (this was not needed had the FS was created and mounted through GUI) -
$ server_mountpoint -create /summit
5) Mount the file system back on to the VDM
$ server_mount ¿o rw summit /summit
6) Find the actual path of this file system mounted on VDM - this will also list that the file system is mounted on the VDM
$ server_mount server_4
-- note the path where summit is mounted - it must be /root_vdm_x/summit - where x is the number for the VDM.
7) Create a new NFS Export for the file system :
$ server_export server_4 -P nfs /root_vdm_x/summit -option rw=Client_IP:client_IP root=client_IP:client_IP access=client_IP:client_IP
Please note that the client IP Addresses needs to be mentioned in the command as option
(or)
- Using Celerra Manager ¿ New NFS exports ¿ Select the data mover as sevrer_4 (you don't have any option to choose VDM for NFS export) - Enter the path ¿/root_vdm_x/summit¿ , ignore the drop-down box for choosing file system ¿ Enter IP addresses of unix server in appropriate fields.
8) NFS mount the file system back on server using the new path name ¿
¿datamover_name_or_IP:/root_vdm_x/summit¿ using one of the interface on the server_4 on the Celerra.
Hope this helps - please feel free to revert back, if there is any issue.
Thanks,
Sandip
nandas
6 Operator
•
1.5K Posts
0
August 10th, 2009 08:00
However, if you need a file system to be used by both CIFS and Windows - you can use CLI to create the NFS export and specify the entire mount path for the file system including the vdm root file system in the path.
But, there are many other considerations for Multi-protocol environment like Accesspolicy, User mapping etc. Please refer to the documentation or consult your EMC NAS person for better understanding of your environment and proper suggestions.
My 2 cents
Thanks,
Sandip
Rainer_EMC
6 Operator
•
8.6K Posts
0
August 10th, 2009 09:00
So if you need to make data from that fs available through an existing CIFS server on a VDM the easiest way to do this is to remount the fs onto that VDM and change the NFS export and client mounts.
You might be able to get around changing the NFS client mountpoint change by using NFS alias.
Alternatively you could create a new CIFS server on the physical data mover and share that fs there.
BUT then you dont have the VDM benefits for replication and seggregation - for example the C$ share on that CIFS server gives potentially access to all VDM mounted file systems.
Rainer_EMC
6 Operator
•
8.6K Posts
0
August 10th, 2009 09:00
yes
no, a file system can only be mounted once (read-write)
If right now your file system is mounted on the physical data mover then your NFS export is like /
When you mount a file system on a VDM its actually mounted on the VDM root so the NFS export becomes something like /root_vdm_ /
that means your NFS clients would have to mount /root_vdm_ / instead of /
You might be able to keep the / export as an alias (search the forum here for NFS alias)
BUT it can get quite confusing if you dont fully understand it so unless changing your NFS client mounts is a big hassle I wouldnt recommend it.
basically server_umount, server_mount and server_export
I really recommend creating a small test file system to test this before doing it on a production file system.
Keep in mind that when you change the mount your NFS clients will fail and have to remount with the new path
Kushi2
1 Rookie
•
82 Posts
0
August 10th, 2009 09:00
I understood your thoughts on what can be done to share an NFS mount. I am totally okay in understanding 'creating a new CIFS server and sharing the file system', but i have few questions and concerns on other alternative (remounting the fs on VDM)
- For remounting the file system, do we need to unmount from server_4 and again remount it on VDM? ( can it be mounted on both server_4 and VDM?)..
- I didn't get the ur point 'changing the NFS export' -- what does that mean?
- Can you please send the commands to implement the change.
Thanks in advance.
nandas
6 Operator
•
1.5K Posts
0
August 10th, 2009 10:00
Rainer_EMC
6 Operator
•
8.6K Posts
1
August 10th, 2009 10:00
Celerra Manager when the file system is mounted on a VDM.
Unlike CIFS servers the NFS server is global on the physical data mover.
It doesnt really care where on the whole data mover the file system is.
BUT for some reason if you use the Celerra Manager GUI to create an NFS export it will not show you VDM mounted file systems in the list to select from.
If you figure out the real path of the fs using a "server_mount" command you can happily NFS export it from Celerra Manager as well.
That path simply is /root_vdm_ / where number is a unique number auto-assigned by the system when the VDM is created
If you only have ever created one VDM its /root/vdm_1
That number gets incremented every time a new VDM is created, even if old ones are deleted they are still "reserved"
So if you created and deleted 30 VDM it would be /root_vdm_30
system including the vdm root file system in the path.
yes using the full path you can use the server_export command
You can also create the export using the CLI and then later modify it via the GUI
Rainer_EMC
6 Operator
•
8.6K Posts
0
August 10th, 2009 11:00
I agree its not really intuitive to just ignore the fs dropdown box.
I will attach some screenshots to hopefully make it clearer.
As you found out you will only get the Path input box if you have at least one file system mounted on the physical data mover
Rainer
1 Attachment
NFS_export_VDM_fs.pdf
Kushi2
1 Rookie
•
82 Posts
0
August 10th, 2009 14:00
We have our business owner's approval to unmount the NFS client.
So now i can unmount the fs from server_4 and
mount it back to a VDM and then export it. If i understand it correct, steps i would follow are:
File system - summit
1) Unmount the file system from server_4
- server_umount server_4 summit /summit
2) Mount the file system back on to the VDM
- server_mount ¿o rw summit /summit
3) Export it to the unix server:
- server_export -p nfs -o rw /summit
(or)
- Using Celerra Manager ¿ New NFS exports ¿ Enter the path ¿/root_vdm_z/summit¿ ¿ Enter IP addresses of unix server in appropriate fields.
4) NFS mount the file system back on server using the new path name ¿ ¿/root_vdm_z/summit¿ using one of the interface on Celerra.
5) Share the same file system using the CIFS server ¿abc¿ configured on vdm
Rainer_EMC
6 Operator
•
8.6K Posts
0
August 11th, 2009 01:00
of course all the server_* commands you can also do with the GUI
I would also recommend to read up on access policies since it looks like you want to exchange data between NFS and CIFS clients
Rainer_EMC
6 Operator
•
8.6K Posts
0
August 11th, 2009 02:00
Maybe if enough customers ask for it, we can get it changed.
Just go to Powerlink Home > Support > Request Support > Request a Product Enhancement
click Get Started.
click Accept
select Celerra General as Product
...
then describe that you want to be able to create an NFS export of a VDM mounted file system through Celerra Manager
that currently the file system drop-down box for the NFS export doesnt show any VDM mounted file systems to select
If you want to can attach my attachment to describe the workaround
thanks
Rainer
nandas
6 Operator
•
1.5K Posts
0
August 13th, 2009 13:00
In fact I also get benefited with these discussions - the one which Rainer mentioned (creating NFS export for a FS mounted on VDM using Celerra Manager) was new to me
So participating in the forums help me as well
Catch you later -
Regards,
Sandip
Kushi2
1 Rookie
•
82 Posts
0
August 13th, 2009 13:00
The process sandip posted was of great help to me. Thanks once again.
I'm actually new to NAS and finding hard time in learning things. Mainly Access policies, getting confused my self while reading too much stuff on powerlink.
Hope I'll get through all difficulties in understanding the topics. With your help ofcourse.
You guys are great.
Peter_EMC
674 Posts
0
December 19th, 2012 03:00
Just create a share for your windows users of the filesystem fs-nfs-lifescicam.
Blondini56
2 Posts
0
December 19th, 2012 03:00
I'm still confused.
We have a filesystem that is exported as an NFS share that we would also like to be able to access from some windows systems, can someone please explain how we do this with the existing filesystem?
The filesystem is fs-nfs-lifescicam which is on server_3 (on our NS480), we also have a cifs server running on server_3
Thanks Nick