ok so a couple of things.

You keep saying that I'm mounting into a sub-directory but I'm not. I'm mounting into the root bucket which is "/ns1/nfs_bucket" the rest of the command is then my local mount point which is /nfsshare. Here is my command again. Look at it closely and you can see the space.

mount -t nfs -o vers=3 lon6dvvcsecs002:/ns1/nfs_bucket /nfsshare/

My about screen looks different. Are you installing the docker version form github?

I just noticed that in your export host photo you have nfs_user in the all 3 anonuser, anongroup and squashuser but if I look closely at the export summary it looks like you are actually dgp for the anongroup.

If you are installing the docker version are you using virtual machines? The way I have this setup is a vmware virtual machine that has a second vmdk added. This is the only thing I can think that is causing my problem.

The good news is I'm not getting any permissions errors. It's only this IO error when I try to write a file.

Sure I would be more than happy to do a webex with you. Should we take the

conversation offline through email or something?

On Thu, Apr 28, 2016 at 9:45 AM benschumacher

I just did another fresh install. These are my steps.

- I installed a minimal copy of centos

- I installed docker, wget, development-tools, git, tar and a couple other basic packages

- I added another vmdk to the vm

- I verified all the system requirments. I have 4 cpus, 16GB of memory, 200GB raw disk as sdb, CentOS Linux release 7.2.1511, Docker Version:1.9.1

- I cloned the github repo https://github.com/EMCECS/ECS-CommunityEdition.git

- I ran the step1 script and I was able to hit the web ui page.

- I ran the step2 script.

- I logged in as root and changed the password.

- I looked at the about page and it looked like your picture. So that's goo news.

- I trying clicking on other pages and the webui is basically frozen and unresponsive.

- I restarted the docker container and waited 10 minutes. I was able to login again

- The about page looks broken again.

- I went to "File" --> "User/Group Mapping" and created nfs_user (500) and nfs_group (501)

- I went to "Users" and created and Object user named nfs_user

- I went to "Buckets" and created a new bucket with the following parameters

  Name: nfs_bucket

  Bucket Owner: nfs_user

  File System: Enabled

  Default Bucket Group: nfs_group

  Group File Permissions: Read Write

  Group Directory Permissions: Read Write

  Bucket Retention: 1 second

- I went to "File" and created a new Export on the nfs_bucket

- I "Add" a new Export Host Option with the following parameters

  Export Host: *

  Permissions: Read/Write

  Authentication: Sys

  AnonUser: nfs_user

  AnonGroup: nfs_group

  RootSquash: nfs_user

- I saved the export

I go to my linux client and run these commands:

[root@ric1pdvcsmgt02 ~]# mkdir /nfs_bucket

[root@ric1pdvcsmgt02 ~]# chmod 777 /nfs_bucket

[root@ric1pdvcsmgt02 ~]# showmount -e 10.72.236.55

Export list for 10.72.236.55:

/ns1/nfs_bucket *

[root@ric1pdvcsmgt02 ~]# mount -t nfs -o vers=3,sec=sys,proto=tcp,async 10.72.236.55:/ns1/nfs_bucket /nfs_bucket

[root@ric1pdvcsmgt02 ~]# cd /nfs_bucket/

[root@ric1pdvcsmgt02 nfs_bucket]# ls

[root@ric1pdvcsmgt02 nfs_bucket]# echo "Test data into my file" > test

-bash: test: Remote I/O error

[root@ric1pdvcsmgt02 nfs_bucket]# ls -al

total 1

drwxrwxrwx. 3 500 501 96 Apr 28 12:49 .

[root@ric1pdvcsmgt02 nfs_bucket]#

I've literally done this same process 25 times using various ecs versions, linux flavors, and nfs clients. I've installed it in 3 different data centers all over the world, I tried different vmware scsi adapters and vmware nic adapters.

I can't help but to conclude this software is a POS and shouldn't be used for NFS. The documentation is terrible and frankly it feels like nfs was an after thought with the 4 or 5 sentences in the manual about it. It by no means explains how to configure the exports.

I appreciate your help Ben. Without you I'd be all alone out here. Do you work for emc? Contact me at danny.caperton @ gmail

Ben!!! You sir are the man! I can't tell you how happy I am you found that. It's all working for me now. I have the export mounted on 2 servers and I'm writing data.

Thanks for sticking with me on this. It's been a beat down to say the least.

On our CE installation in our lab.  I'm able to do everything, but I'm not mounting to a sub directory.  How are you creating /nfsshare above?  Can you please try removing the /nfsshare and mount directly to the root of the bucket?

[root@localhost mnt]# showmount -e 10.1.83.115

Export list for 10.1.83.115:

/nfs/data *

[root@localhost mnt]# mount -t nfs -o vers=3,sec=sys,proto=tcp,async 10.1.83.115:/nfs/data

mount: can't find 10.1.83.115:/nfs/data in /etc/fstab

[root@localhost mnt]# mount -t nfs -o vers=3,sec=sys,proto=tcp,async 10.1.83.115:/nfs/data /mnt/data/

[root@localhost mnt]# cd /mnt/data/

[root@localhost data]# ls

[root@localhost data]# echo 'test data on the new mount.' > test.txt

[root@localhost data]# ls

test.txt

[root@localhost data]# cat test.txt

test data on the new mount.

[root@localhost data]# mkdir dir1

[root@localhost data]# cd dir1/

[root@localhost dir1]# ls

[root@localhost dir1]# cd ..

[root@localhost data]# ls -la

total 2

drwxrwxrwx. 3 500 501 96 Apr 27 18:07 .

drwxr-xr-x. 3 500 501 96 Apr 27 18:07 dir1

-rw-r--r--. 1 500 501 28 Apr 27 18:07 test.txt

[root@localhost data]# cd dir1/

[root@localhost dir1]# touch file

[root@localhost dir1]# echo 'data into test file in test dir1' > dir.txt

[root@localhost dir1]# ls

dir.txt  file

[root@localhost dir1]# cat dir.txt

data into test file in test dir1

[root@localhost dir1]# cat file

[root@localhost dir1]#

The way we have it in our lab is two VMs, each running the single-node 2.2:latest docker image (the default; so it should be the same image you're using, despite the oddity in your GUI).

The second node we added as a separate VDC to the first through the web interface (VDC provisioning can be skipped with an optional flag in step2).

dancaps, Sorry for the confusion.  Yes, I see, you are mounting directly to the root bucket.  Also, the GUI has a bug when viewing an existing host configuration where the anongid value gets populated with the anonuid value.  Any you would be available to look further via WebEx?  Let me know.

Final thought, can you tail the file service logs and run the commands that give you IO errors?  Maybe that will give us a little more information about what's happening.

-Ben

Hey Dan,

You there?

Ben