NFS permissions problem

A

Alexis

New Member
Jun 13, 2014
12
0
1
Hi,
I use a NFS share as storage for my openvz Containers. I have root access to the share :
Code: 
root@safecloud100:~# touch /mnt/pve/CT_Hosting/test.hosting
Code: 
root@MON1-STOR1:/export/home/admin# ls -l /volumes/DefaultVolume/OPENVZ_SAFECLOUD/
total 11
drwxr-xr-x 2 root nobody 2 Jul  7 11:37 dump
drwxr-xr-x 2 root root   2 Jun 20 18:21 images
drwxr-xr-x 3 root nobody 4 Jul 11 11:32 private
drwxr-xr-x 3 root root   3 Jun 18 09:31 template
[COLOR=#ff0000][U]-rw-r--r-- 1 root root   0 Jul 11 11:50 test.hosting[/U][/COLOR]
drwxr-xr-x 2 root root   2 Jul 11 11:31 vztmp
But still when I create a CT i still have these errors :
Code: 
Creating container private area (/mnt/pve/Templates_ISO/template/cache/debian-7-turnkey-appengine-go_13.0-1_amd64.tar.gz)
Performing postcreate actions
/bin/cp: preserving permissions for `/var/lib/vz/root/100/etc/crontab.5483': Operation not supported
/bin/cp: preserving permissions for `/var/lib/vz/root/100/etc/cron.d/cron-apt.5483': Operation not supported
CT configuration saved to /etc/pve/openvz/100.conf
Container private area was created
TASK OK
While the container is created, and it can boot , the DNS server and hostname settings are not passed on by proxmox.
I'm out of idea. Can anyone help me?
 
Tafaul Mujahidin said:
i have same problem

mount error: mount.nfs: requested NFS version or transport protocol is not supported (500)

any body help???
Click to expand...

looks like your NFS server is not providing the right version/features. default, we use NFSv3. if your server requires specific settings, you can set them in /etc/pve/storage.cfg
 
How about my problem? This guy just posted a completely different problem than mine in the thread I started!
 
post all details about your NFS server.
 
What kind of info do you need?
Its a Nexenta server.
server.png
share.png
Code: 
root@safecloud100:~# mount -v
192.168.52.31:/volumes/DefaultVolume/OPENVZ_SAFECLOUD2 on /mnt/pve/CT_hosting2 type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.52.31,mountvers=3,mountport=62434,mountproto=udp,local_lock=none,addr=192.168.52.31)
Do you need any other info?
 
If you use a NFS server on a Solaris based OS you need to add this mount option to /etc/pve/storage.cfg: noacl

An example for my own pve:
Code: 
nfs: omnios_nfs
       path /mnt/pve/omnios_nfs
       server 172.16.2.2
       export /vMotion/nfs
       options vers=3,tcp,nolock,noacl,timeo=20
       content images,rootdir,backup
       maxfiles 2

Forgot to explain why:
The reason for noacl is that Solaris acl is not compatible with linux acl since Solaris uses NFSv4 acl's which is not supported in Linux. Linux acl is based on a Posix draft dated 2002 which has since been withdrawn.
Read: http://crypt47.blogspot.dk/2012/05/linux-acls-vs-solaris-acls.html
 
Last edited:
You must log in or register to reply here.
Top Bottom