nfs client not working in CentOS CT [Synology to blame?]

[mystique]

Hello all,

Hopefully this is trivial.. But I'm a little stumped..

This could also be user error.. I have a "Synology Device" that I have been gifted and was looking at how I could possibly integrate it..

DiskStation is the Synology Device (DS213+ Running the latest 4.3-3810 with NFSv4 Configured; NFS version seems to make no difference..)

#

[root@vmcentos mnt]# showmount -e diskstation
Export list for diskstation:
/volume1/SHR 192.168.1.0/255.255.255.0

[root@vmcentos mnt]# mount.nfs4 diskstation:/volume1/SHR /mnt/nfs -v
mount.nfs4: timeout set for Thu Feb 13 17:44:04 2014
mount.nfs4: trying text-based options 'addr=192.168.1.128,clientaddr=192.168.1.200'
mount.nfs4: mount(2): No such device
mount.nfs4: No such device

[root@vmcentos mnt]# rpm -qa | grep nfs
nfs-utils-1.2.3-39.el6.i686
nfs-utils-lib-1.1.5-6.el6.i686

[root@vmcentos mnt]# grep nfs /proc/filesystems
nodev nfs
nodev nfs4

[root@vmcentos mnt]# service rpcbind status
rpcbind (pid 5674) is running...


# EOF

This *looks* like something on the Synology device is the culprit, but as it's a Snow day here (Lat: 41.64°N Lon: 73.88°W Elev: 155ft.) maybe I'm missing something because of that..

Will try with a Debian7 container when time allows it..

Will also try and get into the Synology and see what I can see..

Open to any suggestions..

Thanks in advance.

pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6)
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-9
libpve-access-control: 3.0-8
libpve-storage-perl: 3.0-18
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1

 

[mystique]

So fighting the wrong fight..

vzctl set 200 --features "nfs:on" --save

This ultimately is what got "nfs to work in the container".. again if you want to fight that fight..

had to get in on the cli on the proxmox host in order to run that.. and had to be done for each host that I wanted to mount the nfs share on the synology..

Again is what I thought I wanted.. but that meant having nfs running in each container..

As long as I was going to have to get in on the cli why not kill more birds with less stones..

openvz bind mounts were the solution that seemed to work the best..

If I mounted the nfs share on the proxmox host I could mount/share that to each container..

#!/bin/bash
. /etc/vz/vz.conf
. ${VE_CONFFILE}
SRC1=/mnt/nfs
DST1=/mnt/nfs


mount -n -t simfs ${SRC1} ${VE_ROOT}${DST1} -o ${SRC1}

I named this 201.mount and placed it inside the /etc/vz/conf/ folder (which at this time is a symbolic link to /etc/pve/openvz/)

and reloaded the 201 container..

root@vmubuntu:~# mount | grep nfs
/mnt/nfs on /mnt/nfs type simfs (rw,relatime)

root@vmubuntu:~# df -h | grep nfs
/dev/simfs      2.7T  239M  2.7T   1% /mnt/nfs

Which gets me nfs running on the proxmox host, and I can mount the share in all the containers that I wish..

#win

YMMV

http://www.jamescoyle.net/how-to/689-mount-nfs-volume-in-a-proxmox-openvz-container

http://www.jamescoyle.net/how-to/525-proxmox-bind-mount-mount-storage-in-a-container

Ironically I found this site hours apart from each other and as you can see it is the same guy

No one said problem solving is linear or efficient..