Hello friends. I have OpenMediaVault running on my server. Within OMV I have a virtual machine, Ubuntu Server 14.04.1 with ownCloud. I'd like to set up NFS so the ownCloud data directory points to a share that pipes back to my RAID mirror on my server. I'm having difficulty in doing so as when I successfully mount it, the owner/group is nobody:4294967294. I've Googled high and low and all I can find are references that I need to change the idmapd setting, which I've done, yet I have no luck. Something a bit concerning is a lot of complaints are online about people having issues with NFS, these same issues, citing that the kernel memory is to blame as NFS's resource requirement is higher than the default kernel memory setting. Some people say just increase it, others say that's an issue as a DDoS or similar attack could fill the kernel's memory and cause it to take a nose dive. Well, I tested it, and I still haven't had any luck. Due to my level of exhaustion I figured I'd post here to see what you folks thought, as I admit NFS is not my strong point.
The system named "vault" is OpenMediaVault, whereas the system named "owncloud" is the actual virtual machine. OMV's IP is .200, the VM is .202.
How I'm mounting and the ownership/group issue I'm seeeing:
Zitat
root@owncloud:/mnt# mount -t nfs 192.168.1.200:/owncloud /mnt/OC_DATA_NFS/
root@owncloud:/mnt# ls -l
total 4
drwxrwsr-x 2 nobody 4294967294 4096 Dec 24 11:22 OC_DATA_NFS
The VM's /etc/default/idmapd.conf
ZitatAlles anzeigenroot@owncloud:/mnt# cat /etc/default/nfs-common
# If you do not set values for the NEED_ options, they will be attempted
# autodetected; this should be sufficient for most people. Valid alternatives
# for the NEED_ options are "yes" and "no".
# Do you want to start the statd daemon? It is not needed for NFSv4.
NEED_STATD=no
# Options for rpc.statd.
# Should rpc.statd listen on a specific port? This is especially useful
# when you have a port-based firewall. To use a fixed port, set this
# this variable to a statd argument like: "--port 4000 --outgoing-port 4001".
# For more information, see rpc.statd(8) or http://wiki.debian.org/SecuringNFS
STATDOPTS=
NEED_IDMAPD=yes
# Do you want to start the gssd daemon? It is required for Kerberos mounts.
NEED_GSSD=
The VM's /etc/idmapd.conf
ZitatAlles anzeigen[General]
Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
# set your own domain here, if id differs from FQDN minus hostname
Domain = localdomain
[Translation]
Method = nsswitch
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
OMV's /etc/default/nfs-common
ZitatAlles anzeigen
root@vault:/etc# cat /etc/exports
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
/export/owncloud 192.168.1.202/24(rw,subtree_check,secure)
# NFSv4 - pseudo filesystem root
/export 192.168.1.202/24(ro,fsid=0,root_squash,no_subtree_check,hide)
root@vault:/etc# cat /etc/default/nfs-common
# If you do not set values for the NEED_ options, they will be attempted
# autodetected; this should be sufficient for most people. Valid alternatives
# for the NEED_ options are "yes" and "no".
# Do you want to start the statd daemon? It is not needed for NFSv4.
NEED_STATD=
# Options for rpc.statd.
# Should rpc.statd listen on a specific port? This is especially useful
# when you have a port-based firewall. To use a fixed port, set this
# this variable to a statd argument like: "--port 4000 --outgoing-port 4001".
# For more information, see rpc.statd(8) or http://wiki.debian.org/SecuringNFS
STATDOPTS=
# Do you want to start the idmapd daemon? It is only needed for NFSv4.
NEED_IDMAPD=yes
# Do you want to start the gssd daemon? It is required for Kerberos mounts.
NEED_GSSD=
OMV's /etc/idmapd.conf
ZitatAlles anzeigen
root@vault:/etc# cat /etc/idmapd.conf
[General]
Verbosity = 0
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
# set your own domain here, if id differs from FQDN minus hostname
Domain = localdomain
[Translation]
Method = nsswitch
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
root@vault:/etc# cat /etc/exports
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
/export/owncloud 192.168.1.202/24(rw,subtree_check,secure)
# NFSv4 - pseudo filesystem root
/export 192.168.1.202/24(ro,fsid=0,root_squash,no_subtree_check,hide)
[/quote]
OMV's /etc/exports:
ZitatAlles anzeigen
root@vault:/etc# cat /etc/exports
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
/export/owncloud 192.168.1.0/24(rw,subtree_check,secure)
# NFSv4 - pseudo filesystem root
/export 192.168.1.0/24(ro,fsid=0,root_squash,no_subtree_check,hide)
If anybody has any idea as to what may be up, I'd love to hear it! Thank you in advance. Merry Christmas!
Edit - side question... I've been reading about nothing but issues and bug reports with nfs. Kind of concerns me. Would mounting it via ssh be a more advisable approach?