Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

9676

August 7th, 2012 08:00

NFS Mount on ESX

I have created Celerra NFS Exports with all required required parameteres **rw/access/root hosts (on file system in VDM and also in server_2)*

Given VMKERNEL IP as shown in primus.

I am able to mount the NFS share from ESX host via VirtualCenter & also via CLI

But when i write file it gives out error as "Call "FileManager.MakeDirectory" for object "FileManager" on vCenter Server"

I can't write any file.

thanks in advance.

96 Posts

August 9th, 2012 00:00

Hi Dynamo - used VMconsole IP's (without deleting other entries - VMKERNEL IP's). Primus shows to use VMKERNEL IP's emc255450....

1 Rookie

 • 

20.4K Posts

August 7th, 2012 10:00

can you add your management ip address to the export list as well ?

96 Posts

August 7th, 2012 10:00

@dynamo - i checked this site... I cannot find "no_root_squash" option in Celerra

1 Rookie

 • 

20.4K Posts

August 7th, 2012 12:00

Management Network (vmk0 on my system)

96 Posts

August 7th, 2012 12:00

got it...

/etc/exports - no file available in ESXi. - the comment i received.

Just an update (which i tested on control station right now):::

I tried a different NFS export on the same file system (also on different file system) and mounted in celerra control station itself.

This is also not able to write any file though i am able to mount in control station.

96 Posts

August 7th, 2012 12:00

I am not a VM guy - i just want to tell them what they needs to do... its ESXi and 4.0.

pl let me know - vmk0 on my system is esx based config? so that i can tell them accordingly...

96 Posts

August 7th, 2012 12:00

Hi Dynamox

Which Management IP?

*control station?

*virtual center?

*or any other?

Thanks

1 Rookie

 • 

20.4K Posts

August 7th, 2012 12:00

Management network port on ESX, typically vmk0

1 Rookie

 • 

20.4K Posts

August 7th, 2012 13:00

when you create NFS export you populated root, access and read-write fields ?

96 Posts

August 7th, 2012 13:00

yes - all pre-requisites are met as post in my first note. (rw/root/access with VMkernel IP's).......

674 Posts

August 7th, 2012 23:00

If you are able to mount but not write, check the permissions on the file system itself (f.e. do a ls -l at the top of the FS).

If even root is not able to write then the FS is not exported for root or it is mounted read only on the datamover itself.

There is no "no_root_squash" option for the export of the FS available.

96 Posts

August 8th, 2012 01:00

mounted in dm as read/write and all filesystem level done appropriately... backend is symmetrix.

[nasadmin@EMCNAS ~]$ nas_fs -i fs1

id        = 44

name      = fs1

acl       = 0

in_use    = True

type      = uxfs

worm      = off

volume    = v405

pool      = R5_Pool_SRDF

member_of = root_avm_fs_group_45

rw_servers= server_2

ro_servers=

rw_vdms   =

ro_vdms   =

auto_ext  = no,thin=no

deduplication   = Off

stor_devs = 00033333xx9-017C

disks     = d15

disk=d15   stor_dev=00033333xx9-017C   addr=c0t1l8-0-0     server=server_2

[nasadmin@EMCNAS ~]$

674 Posts

August 8th, 2012 02:00

Permissions?

> If you are able to mount but not write, check the permissions

> on the file system itself (f.e. do a ls -l at the top of the FS).


674 Posts

August 8th, 2012 03:00

pmenon5 wrote:

ls -l output

drwxr-xr-x 6 root root 1024 Aug  7 16:20 fs1

Means any user other than root is not allowed to write into fs1.

Is this what you want?

Also the server_export needs to fit for this.

If other  users except root should be allowed to write into the fs1, you need to change the permissions of fs1, f.e. chmod 777 fs1 will allow all users to write into fs1

No Events found!

Top