The steps for NFS exporting a file system on a VDM

I made a blog post back in January 2014 about creating an NFS export on a virtual data mover but I didn’t give much detail on the commands you need to use to actually do it. As I pointed out back then, you can’t NFS export a VDM file system from within Unisphere however when a file system is mounted on a VDM its path from the root of the physical Data Mover can be exported from the CLI.

The first thing that needs to be done is determining the physical Data Mover where the VDM resides.

Below is the command you’d use to make that determination:

[nasadmin@Celerra_hostname]$ nas_server -i -v name_of_your_vdm | grep server
server = server_4

That will show you just the physical data mover that it’s mounted on. Without the grep statement, you’d get the output below. If you have hundreds of filesystems it will cause the screen to scroll the info you’re looking for off the top of the screen. Using grep is more efficient.

[nasadmin@Celerra_hostname]$ nas_server -i -v name_of_your_vdm
id = 1
name = name_of_your_vdm
acl = 0
type = vdm
server = server_4
rootfs = root_fs_vdm_name_of_your_vdm
I18N mode = UNICODE
mountedfs = fs1,fs2,fs3,fs4,fs5,fs6,fs7,fs8,…
member_of =
status :
defined = enabled
actual = loaded, active
Interfaces to services mapping:
interface=10-3-20-167 :cifs
interface=10-3-20-130 :cifs
interface=10-3-20-131 :cifs

Next you need to determine the file system path from the root of the Data Mover. This can be done with the server_mount command. As in the prior step, it’s more efficient if you grep for the name of the file system. You can run it without the grep command, but it could generate multiple screens of output depending on the number of file systems you have.

[nasadmin@stlpemccs04a /]$ server_mount server_4 | grep Filesystem_03
Filesystem_03 on /root_vdm_3/Filesystem_03 uxfs,perm,rw

The final step is to actually export the file system using this path from the prior step. The file system must be exported from the root of the Data Mover rather than the VDM. Note that once you have exported the VDM file system from the CLI, you can then manage it from within Unisphere if you’d like to set server permissions. The “-option anon=0,access=server_name,root=server_name” portion of the CLI command below can be left off if you’d prefer to use the GUI for that.

[nasadmin@Celerra_hostname]$ server_export server_4 -Protocol nfs -option anon=0,access=server_name,root=server_name /root_vdm_3/Filesystem_03
server_4 : done

At this point the client can mount the path with NFS.


4 thoughts on “The steps for NFS exporting a file system on a VDM”

  1. Hey SAN Guy,

    This is an excellent post. Many of my Storage buds have come to me wondering why they can’t export to the vdm via Unisphere. OR, why they don’t see ANY exports in the list.

    I’d just like to add 2 things:

    1. It’s not best practice to export from a file system. Should either be from a quota, or create a mountpoint off the FS.
    2. You CAN export from the vdm. Here is a sample command that I just ran which worked fine.

    server_export vdm1 -Protocol nfs -option root=host1:host2,access=host1:host2 -name nfsexport /FS1/nfsexport

      1. Hi,
        Thanks for the post. Following these steps worked for me. I tried Joe’s method but although I can export from the VDM using the CLI the client cannot see it.
        I guess my question is, what do I lose by exporting from the physical DM instead of the VDM that has the filesystem

        1. You don’t actually gain or lose anything, it’s just that it has to be done differently with VDM’s (if I’m understanding your question correctly). I don’t have any good explanation as to why the clients wouldn’t see it other than a permissions issue, make sure your export permissions are set properly with the appropriate IP or DNS name of the server for the read-only, read-write, and access lists.

Leave a Reply