Nfs Share within container

[paulwarren]

Hi,

I wonder if someone could help,

I currently have a nas with OVH (1tb) which is connected via a private ip 10.*.*.* address, the Share works fine within the container but we are moving away from the nas to one of the backup servers they offer.

I have installed nfs server on the backup server and have managed to setup a share to the proxmox hardware host e.g prox1

When I try to setup the container which currently has a working nfs share (see below for the fstab)

10.*.*.*:/nas-000000/backup /mnt/backup nfs rw 0 0

Which works fine, When I try to add my new nfs server using the following

mount -t nfs 37.187.130.15:/home/dump /mnt/backupserver

I get the following error


mount.nfs: Protocol not supported

So I decided that maybe I need to have the nfs share mapped as NFS, when I go into the gui and add new storage, select NFS, enter ip, the mount point displays, But when I go to view the content I get the following error

mount error: mount.nfs: Operation not permitted (500)

The /etc/exports on the nfs server looks like the below, with the /etc/hosts.allow as follows.


/home/dump 178.*.*.*(rw,sync,no_subtree_check,no_root_squash) 178.*.*.*(rw,sync,no_subtree_check,no_root_squash) 178.*.*.*(rw,sync,no_subtree_check,no_root_squash)


rpcbind: 178.*.*.*, 62.*.*.*, 178.*.*.*, 178.*.*.*



Does any one have any idea what I am doing wrong, I can't seem to work out what the problem is.

 

[mir]

What version of NFS is running on the new server? (NFSv3, NFSv4 or both)

 

[paulwarren]

nfs v3 and nfs v4 by the looks of things,

See below

nfsstat
Server rpc stats:
calls badcalls badclnt badauth xdrcall
248819 3 0 3 0


Server nfs v2:
null getattr setattr root lookup readlink
6 100% 0 0% 0 0% 0 0% 0 0% 0 0%
read wrcache write create remove rename
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
link symlink mkdir rmdir readdir fsstat
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%


Server nfs v3:
null getattr setattr lookup access readlink
6509 100% 0 0% 0 0% 0 0% 0 0% 0 0%
read write create mkdir symlink mknod
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
remove rmdir rename link readdir readdirplus
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
fsstat fsinfo pathconf commit
0 0% 0 0% 0 0% 0 0%


Server nfs v4:
null compound
1 0% 242303 99%


Server nfs v4 operations:
op0-unused op1-unused op2-future access close commit
0 0% 0 0% 0 0% 15575 2% 24 0% 168 0%
create delegpurge delegreturn getattr getfh link
11 0% 0 0% 2 0% 213078 33% 232 0% 0 0%
lock lockt locku lookup lookup_root nverify
0 0% 0 0% 0 0% 259 0% 0 0% 0 0%
open openattr open_conf open_dgrd putfh putpubfh
111 0% 0 0% 6 0% 0 0% 239534 37% 0 0%
putrootfh read readdir readlink remove rename
3 0% 26077 4% 42 0% 0 0% 9 0% 11 0%
renew restorefh savefh secinfo setattr setcltid
2770 0% 4 0% 14 0% 0 0% 10 0% 2 0%
setcltidconf verify write rellockowner bc_ctl bind_conn
2 0% 0 0% 142181 22% 0 0% 0 0% 0 0%
exchange_id create_ses destroy_ses free_stateid getdirdeleg getdevinfo
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
getdevlist layoutcommit layoutget layoutreturn secinfononam sequence
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
set_ssv test_stateid want_deleg destroy_clid reclaim_comp
0 0% 0 0% 0 0% 0 0% 0 0%


Client rpc stats:
calls retrans authrefrsh
0 0 0

 

[mir]

I guess your problem is then that your NFS server defaults to use NFSv4 according to NFS specifications ("if no version is specified choose the highest version supported by the NFS server and mount command") which is not supported in a container. To overcome this problem you will need to specify to use version 3 of NFS to your mount instruction.

mount -t nfs -o vers=3 37.187.130.15:/home/dump /mnt/backupserver

 

[paulwarren]

I get

mount.nfs: Operation not permitted


is there away to force nfs to use version 3 on the nfs server?