Feb 4, 2013

openSUSE Forums: Trouble using NFS Server on OpenSUSE 12.2

openSUSE Forums
openSUSE Forums
Trouble using NFS Server on OpenSUSE 12.2
Feb 4th 2013, 14:01

I'm trying to use a new install of OpenSUSE 12.2 to provide an NFS share to an vmware esxi host but am having problems getting the share working. I was hoping the suse community might be able to help me out.

Requirement: NFS v3 share over TCP to a number of esxi Hosts mounted with root access & read write permissions.
What I've done so far
  • Installed OpenSUSE 12.2 from DVD and chose LVM, SAMBA (to join to a Windows Domain) & KDE during install. and configured networking
  • Installed any updates that were needed.
  • Used Yast to install NFS Server & Client and followed openSUSE 12.2: Chapter 18. Sharing File Systems with NFS to setup a share /ShareNFS/Share1 and export it using yast gui


Problem
When I try to connect from the esx host it says the mount has been denied by the server but from my (very basic) experience it looks like I have everything setup but I've obviously missed something.

What I've tried
  • Disabling the Firewall
  • Using the IP address, FQDN, hostname as the server address when trying to connect
  • Mounting the Share onto a Windows Computer but that also failed.
  • I can ping from windows in same network to OpenSUSE and vis versa
  • I can ping from OpenSUSE to both esxi hosts
  • ESXi hosts previously mounted a NFS Share from windows successfully (performance was terrible so decided to use OpenSUSE) on same hardware and same network connection


My Settings: (didn't restrict by IP address until I can get connection working)
/etc/exports
/ShareNFS/Share1 *(rw,no_root_squash,sync)


Services
According to System Services (Runlevel) nfsserver is running at levels 3 & 5
chkconfig nfs is ON
chkconfig nfsserver is ON

/etc/syconfig/nfs
## Path: Network/File systems/NFS server
## Description: number of threads for kernel nfs server
## Type: integer
## Default: 4
## ServiceRestart: nfsserver
#
# the kernel nfs-server supports multiple server threads
#
USE_KERNEL_NFSD_NUMBER="4"


## Path: Network/File systems/NFS server
## Description: use fixed port number for mountd
## Type: integer
## Default: ""
## ServiceRestart: nfsserver
#
# Only set this if you want to start mountd on a fixed
# port instead of the port assigned by rpc. Only for use
# to export nfs-filesystems through firewalls.
#
MOUNTD_PORT=""


## Path: Network/File systems/NFS server
## Description: GSS security for NFS
## Type: yesno
## Default: yes
## ServiceRestart: nfs nfsserver
#
# Enable RPCSEC_GSS security for NFS (yes/no)
#
NFS_SECURITY_GSS="no"


## Path: Network/File systems/NFS server
## Description: NFSv3 server support
## Type: yesno
## Default: yes
## ServiceRestart: nfsserver
#
# Enable NFSv3 server support (yes/no)
# This causes the NFS server to respond to
# NFSv2 and NFSv3 requests. Only disable this
# if you want to ensure only NFSv4 is used.
#
NFS3_SERVER_SUPPORT="yes"


## Path: Network/File systems/NFS server
## Description: NFSv4 protocol support
## Type: yesno
## Default: yes
## ServiceRestart: nfs nfsserver
#
# Enable NFSv4 support (yes/no)
#
NFS4_SUPPORT="no"


## Path: Network/File systems/NFS server
## Description: Network Status Monitor options
## Type: string
## Default: ""
#
#
SM_NOTIFY_OPTIONS=""


## Path: Network/File systems/NFS server
## Description: Always start NFS services
## Type: yesno
## Default: yes
## ServiceRestart nfs
#
# Always start NFS services (gssd, idmapd), not only if
# there are nfs mounts in /etc/fstab. This is likely to be
# needed if you use an automounter for NFS.
# Note that the nfs service is no longer enabled by default
# and the command "chkconfig nfs on" is needed to fully enable
# NFS.
#
NFS_START_SERVICES="yes"


## Path: Network/File systems/NFS server
## Description: Command line parameters for rpc.statd
## Type: string
## Default: ""
#
# Custom parameters for rpc.statd daemon. Typically this will
# be used to set the port number (-p).
#
STATD_OPTIONS=""


## Path: Network/File systems/NFS server
## Description: Lease time for NFSv4 leases
## Type: integer
## Default: ""
#
# Set the lease time for the NFSv4 server. This allows new locks
# to be taken sooner after a server restart, so it is useful for
# servers which need to recover quickly after a failure, particularly
# in fail-over configurations. Reducing the lease time can be a
# problem is some clients connect over high latency networks.
# The default is 90 seconds. A number like 15 might be appropriate
# in a fail-over configuration with all clients on well connected
# low latency links.
NFSV4LEASETIME=""


## Path: Network/File systems/NFS server
## Description: Alternate mount point for rpc_pipefs filesystem
## Type: string
## Default: ""
#
# In a high-availabilty configuration it is possible that /var/lib/nfs
# is redirected so some shared storage and so it is not convenient to
# mount the rpc_pipefs filesystem at /var/lib/nfs/rpc_pipefs. In that
# case an alternate mount point can be given here.
RPC_PIPEFS_DIR=""


## Path: Network/File systems/NFS server
## Description: Options for svcgssd
## Type: string
## Default: ""
#
# Normally svcgssd does not require any option. However in a
# high-availabilty configuration it can be useful to pass "-n"
# to guide the choice of default credential. To allow for that
# case or any other requiring options ot svcgssd, they can
# be specified here.
SVCGSSD_OPTIONS=""


## Path: Network/File systems/NFS server
## Description: Extra options for nfsd
## Type: string
## Default: ""
#
# This setting allows extra options to be specified for NFSD, such as
# -H <shared_hostname> in a high-availability configuration.
NFSD_OPTIONS=""

You are receiving this email because you subscribed to this feed at blogtrottr.com.

If you no longer wish to receive these emails, you can unsubscribe from this feed, or manage all your subscriptions

No comments: