NFS storage addition problem

K

kn2mUc

Renowned Member
Jan 30, 2016
26
0
66
43
Im trying to add NFS storage to proxmox 4.3-14/3a8c61c7.
Im using Napp-it as my NAS. I created a NFS share, set the access rights as follows

Code: 
ACL   User/ Group   acl   acl-set   details   inheritance   type   option
              
0   user:root   rwxpdDaARWcCos   full_set   rd(acl,att,xatt) wr(acl,att,xatt,own) add(fi,sdir) del(yes,child) x, s   file,dir   allow   delete
1   everyone@   rwxpdDaARWc--s   modify_set   rd(acl,att,xatt) wr(att,xatt) add(fi,sdir) del(yes,child) x, s   file,dir   allow   delete

I can access the NFS folder, create files etc from my laptop which is in the same subnet as both the nappit and proxmox machines. I can add the folder in promos, summary and permissions work fine but but when I try to look at the contents the web page hangs and I see the following error

Code: 
mkdir /mnt/pve: Permission denied at /usr/share/perl5/PVE/Storage/NFSPlugin.pm line 133. (500)

Not quite sure where to attempt to fix this error at, any pointers would be appreciated. Thanks in adv
 
SSH to the proxmox head. cd /mnt/pve/<NAPP-IT mount point>

$ touch fred

Can you create? NO, then you still have a permissions issue on your Filer.
 
hey Guy,
I don't have anything under /mnt

Code: 
root@proxmox:/# cd /
root@proxmox:/# ls /mnt
root@proxmox:/#

root@proxmox:/# mkdir /mnt/pve
mkdir: cannot create directory ‘/mnt/pve’: Permission denied

A SMB share from 'PVEbackups' was working just fine before I decommissioned that server.

proxstoargeerr.png proxstorage.png
 
very strange, seems you have no writeaccess with root. Can you touch or mkdir on another place on the server? What says "mount"?
 
fireon said:
very strange, seems you have no writeaccess with root. Can you touch or mkdir on another place on the server? What says "mount"?
Click to expand...

Thanks for taking the time to respond. Yes, my root user appears locked out of using /mnt which I presume is why it can't mount the NFS shares. I can however access other locations, for example

Code: 
root@proxmox:/# mkdir /mnt/test
mkdir: cannot create directory ‘/mnt/test’: Permission denied
root@proxmox:/# mkdir /test
root@proxmox:/# echo "test" > /test/test.txt
root@proxmox:/# cat /test/test.txt
test
root@proxmox:/# touch /test/test.txt
root@proxmox:/#

I've restarted both filer & proxmox and created a ground up new pool and NFS share with the following Napp-it parameters which should allow any device in the 192.168.20.0 subnet read/write access and proxmox (192.168.20.12) root access

Code: 
rw=@192.168.20.0/24,root=@192.168.20.12/32 SSDpool/SSDdata

I verified I can connect to this NFS from my Mac.

I add the new NFS share into proxmox,

proxmoxaddnfs.png

everything adds into the GUI fine however I see this error in the syslog file

Code: 
Dec 18 12:44:19 proxmox automount[3157]: key "pve" not found in map source(s).
Dec 18 12:44:19 proxmox pvestatd[3299]: mkdir /mnt/pve: Permission denied at /usr/share/perl5/PVE/Storage/NFSPlugin.pm line 133.

and the drive isn't mounted

Code: 
root@proxmox:~# ls /mnt
root@proxmox:~#

If I could fix the writing into /mnt I suspect this would be resolved but Im not sure how on earth to go about that, other than a fresh install.

Heres the output of mount
Code: 
root@proxmox:~# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=8239157,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,relatime,size=13201688k,mode=755)
rpool/ROOT/pve-1 on / type zfs (rw,relatime,xattr,noacl)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=21,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
rpool on /rpool type zfs (rw,noatime,xattr,noacl)
rpool/ROOT on /rpool/ROOT type zfs (rw,noatime,xattr,noacl)
rpool/data on /rpool/data type zfs (rw,noatime,xattr,noacl)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
/etc/auto.smb-shares on /mnt type autofs (rw,relatime,fd=6,pgrp=3157,timeout=300,minproto=5,maxproto=5,indirect)

Also tried upgrading to 4.4, heres the pvevefsion data
Code: 
root@proxmox:~# pveversion -v
proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
pve-kernel-4.4.24-1-pve: 4.4.24-72
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80
 
Last edited:
like this, right?

nfs: testNFS
server 192.168.20.20
path /mnt/pve/testNFS
export /SSDpool/SSDdata
content images
options vers=3
maxfiles 1
noacl
 
No, like this:
nfs: testNFS
server 192.168.20.20
path /mnt/pve/testNFS
export /SSDpool/SSDdata
content images
options vers=3, noacl
maxfiles 1
 
  • Like
Reactions: kn2mUc
What says
Code: 
ls -ld /mnt
getfacl /mnt
setfacl -b /mnt
chmod 777 /mnt
ls -ld /mnt
mkdir /mnt/blabla
 
fireon said:
What says
Code: 
ls -ld /mnt
getfacl /mnt
setfacl -b /mnt
chmod 777 /mnt
ls -ld /mnt
mkdir /mnt/blabla
Click to expand...

Code: 
root@proxmox:~# ls -ld /mnt
drwxr-xr-x 2 root root 0 Dec 18 17:22 /mnt
root@proxmox:~# getfacl /mnt
getfacl: Removing leading '/' from absolute path names
# file: mnt
# owner: root
# group: root
user::rwx
group::r-x
other::r-x

root@proxmox:~# setfacl -b /mnt
root@proxmox:~# chmod 777 /mnt
root@proxmox:~# ls -ld /mnt
drwxrwxrwx 2 root root 0 Dec 18 17:22 /mnt
root@proxmox:~# mkdir /mnt/blabla
mkdir: cannot create directory ‘/mnt/blabla’: Permission denied
 
mir said:
No, like this:
nfs: testNFS
server 192.168.20.20
path /mnt/pve/testNFS
export /SSDpool/SSDdata
content images
options vers=3, noacl
maxfiles 1
Click to expand...

ahhhh, fixed, thank you. No difference immediately obvious. Does this need a restart or anything to take affect?
 
I really appreciate you guys taking the time to help, Ive been unable to make this work, its clearly beyond my Linux comprehension so I gave up and created a fresh install this afternoon on a spare hard disk and was able to mount both ZFS and NFS volumes without any trouble at all. I'll try and transfer across my disk images from the old disk to the new install and hopefully things should be good from here on. Thanks again.
 
You must log in or register to reply here.
Top Bottom