[SOLVED] Problem mounting nfs shares

Hello everybody,
I keep getting the following error when I try to mount an NFS share;
mount.nfs4: an incorrect mount option was specified
The corresponding line in /etc/fstab is this:
pc-francois.local:/francois /mnt/pc-francois nfs4 rw,port=2049,noauto,users,intr 0 0
showmount -e pc-francois.local gives this:
Export list for pc-francois.local:
/export/archives 192.168.1.0/24
/export/portage 192.168.1.0/24
/export/francois 10.8.0.0/24,192.168.1.0/24
/export 10.8.0.0/24,192.168.1.0/24
Finally, the nfs related modules are loaded. lsmod | grep nfs gives this:
nfsv4 129119 0
nfsd 228113 13
auth_rpcgss 41857 1 nfsd
nfs 118782 1 nfsv4
lockd 57996 2 nfs,nfsd
grace 1706 2 nfsd,lockd
sunrpc 170119 19 nfs,nfsd,auth_rpcgss,lockd,nfsv4
It works perfectly fine from other client not running on arch linux. Like indicated in the howto, I have enabled and started the services rpcbind.service,nfs-client.target and remote-fs.target
Can somebody explains what is happening ?
Last edited by FrançoisVal (2015-05-02 16:48:14)

I finally solved my problem by changing the mount options to this in fstab:
pc-francois.local:/francois /mnt/pc-francois nfs4 rw,proto=tcp,vers=4.0,noauto,users,intr 0 0
One week to find it... Maybe it wants to use nfs 4.1 by default.

Similar Messages

Mounting nfs shares takes much longer since updating to 10.3.9

Hi, first post here. The titles of the forums are vague and I hope "getting online" really is the "networking forum"; apologies if not.
I have two linux machines which I regularly mount nfs shares from onto my powerbook. These machines are on the LAN and have known IP's for netinfod so I don't think the following problem is DNS related.
Since the last 10.3.9 update, mounting these shares (via finder or command line mount_nfs) has become very unreliable. Sometimes they never seem to mount, sometimes almost immediately, and other times they mount eventually even though I might of canceled the dialog box waiting for the mount. The logs show:
mount_nfs: bad MNT RPC: RPC: Timed out
The server side logs show only repeated authentication approvals. The servers have not changed software -- only OSX has been updated.
Independent if I use WiFi or a landline.
Once the shares are mounted, there is no detectable connection problems at all. Was any part of the NFS client updated in 10.3.9? Any ideas what might be wrong. TIA.
12" PowerBook G4 Mac OS X (10.3.9)

Just to bump this, as no one has chimed in, I found the problem and I will post the fix only if someone asks. It's not stupid, and it might help you. I am surprised that no one cares.
I'd still like to know why you can't launch PS from a bootable backup.

Cannot mount nfs shares

Hello,
since Sunday I'm unable to mount NFS shares:
mount.nfs: No such device
The server-side is working fine, I can mount all shares from my FreeBSD Desktop machine.
I'm using netcfg and start rpcbind and nfs-common upong connection before mounting NFS shares (via netfs). Is this maybe related to some recent pacman updates? It was working flawless just until Sunday.

As it turns out, It now works. I did load the nfs module manually during my troubleshooting but it was already loaded or built into the kernel or whatever.
The thing that made it work is changing the nfs mount lines in /etc/fstab from the hostname of the server to the ip address of the server. I don't know why that worked on both machines since I could ping the hostname of the nfs server which is a Freenas server and it always worked before.
@ jasonwryan
rc.d start rpcbind && rc.d start nfs-common
start fine after stopped and restarted. Have you replaced portmap with rpcbind in pacman? rpcbind superceded portmap a while back. gl.
@.:B:.
lol, snide remark succesfully detected. In my defense I was half guessing and half sniding (or some percentage thereof). I have to admit I do get a bit snippy over this since nfs is necessary for my little clients to run mpd and I gets a bit cranky when I gots no musics! Fueling my frustration, it seems I have to chase down nfs problems frequently after "pacman -Syu".

NFS4: Problem mounting NFS mount onto a Solaris 10 Client

Hi,
I am having problems mounting NFS mount point from a Linux-Server onto a Solaris 10 Client.
In the following
=My server IP ..*.120
=Client IP ..*.100
Commands run on Client:
==================
# mount -o vers=3 -F nfs 172.25.30.120:/scratch/pvfs2 /scratch/pvfs2
nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive
nfs mount: retrying: /scratch/pvfs2
nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive
nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive
# mount -o vers=4 -F nfs 172.25.30.120:/scratch/pvfs2 /scratch/pvfs2
nfs mount: 172.25.30.120:/scratch/pvfs2: No such file or directory
# rpcinfo -p
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
1073741824 1 tcp 36084
100024 1 udp 42835 status
100024 1 tcp 36086 status
100133 1 udp 42835
100133 1 tcp 36086
100001 2 udp 42836 rstatd
100001 3 udp 42836 rstatd
100001 4 udp 42836 rstatd
100002 2 tcp 36087 rusersd
100002 3 tcp 36087 rusersd
100002 2 udp 42838 rusersd
100002 3 udp 42838 rusersd
100011 1 udp 42840 rquotad
100021 1 udp 4045 nlockmgr
100021 2 udp 4045 nlockmgr
100021 3 udp 4045 nlockmgr
100021 4 udp 4045 nlockmgr
100021 1 tcp 4045 nlockmgr
100021 2 tcp 4045 nlockmgr
100021 3 tcp 4045 nlockmgr
100021 4 tcp 4045 nlockmgr
# showmount -e 172.25.30.120 (Server)
showmount: 172.25.30.120: RPC: Rpcbind failure - RPC: Unable to receive
Commands OnServer:
================
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100021 1 tcp 49927 nlockmgr
100021 3 tcp 49927 nlockmgr
100021 4 tcp 49927 nlockmgr
100021 1 udp 32772 nlockmgr
100021 3 udp 32772 nlockmgr
100021 4 udp 32772 nlockmgr
100011 1 udp 796 rquotad
100011 2 udp 796 rquotad
100011 1 tcp 799 rquotad
100011 2 tcp 799 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 809 mountd
100005 1 tcp 812 mountd
100005 2 udp 809 mountd
100005 2 tcp 812 mountd
100005 3 udp 809 mountd
100005 3 tcp 812 mountd
100024 1 udp 854 status
100024 1 tcp 857 status
# showmount -e 172.25.30.120
Export list for 172.25.30.120:
/scratch/nfs 172.25.30.100,172.25.24.0/4
/scratch/pvfs2 172.25.30.100,172.25.24.0/4
Thank you, ~al

I also tried to run Snoop on the client and wireshark on Server and following is what I see:
One Server: Upon issuing mount command on client:
# tshark -i eth1
Running as user "root" and group "root". This could be dangerous.
Capturing on eth1
0.000000 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
0.205570 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(100005) V:3 UDP
0.205586 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
0.207863 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(100005) V:3 UDP
0.207869 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
2.005314 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
4.011005 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
5.206109 Dell_70:ad:29 -> SunMicro_70:ff:17 ARP Who has 172.25.30.100? Tell 172.25.30.120
5.206277 SunMicro_70:ff:17 -> Dell_70:ad:29 ARP 172.25.30.100 is at 00:14:4f:70:ff:17
5.216157 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(100005) V:3 UDP
5.216170 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
On Clinet Upon issuing mount command on client:
# snoop -d bge1
Using device /dev/bge1 (promiscuous mode)
? -> * ETHER Type=9000 (Loopback), size = 60 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
atlas-pvfs2 -> pvfs2-io-0-3 PORTMAP C GETPORT prog=100005 (MOUNT) vers=3 proto=UDP
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (UDP port 111 unreachable)
atlas-pvfs2 -> pvfs2-io-0-3 PORTMAP C GETPORT prog=100005 (MOUNT) vers=3 proto=UDP
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (UDP port 111 unreachable)
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> * ETHER Type=9000 (Loopback), size = 60 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
pvfs2-io-0-3 -> * ARP C Who is 172.25.30.100, atlas-pvfs2 ?
atlas-pvfs2 -> pvfs2-io-0-3 ARP R 172.25.30.100, atlas-pvfs2 is 0:14:4f:70:ff:17
atlas-pvfs2 -> pvfs2-io-0-3 PORTMAP C GETPORT prog=100005 (MOUNT) vers=3 proto=UDP
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (UDP port 111 unreachable)
Also I see the following on Client:
# rpcinfo -p pvfs2-io-0-3
rpcinfo: can't contact portmapper: RPC: Rpcbind failure - RPC: Failed (unspecified error)
When I try the above rpcinfo command on Client and Server Snoop And wireshark(ethereal) outputs are as follows:
Client # snoop -d bge1
Using device /dev/bge1 (promiscuous mode)
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
atlas-pvfs2 -> pvfs2-io-0-3 TCP D=111 S=872 Syn Seq=2065245538 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK>
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (TCP port 111 unreachable)
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=2004 (Unknown), size = 48 bytes
? -> (multicast) ETHER Type=0003 (LLC/802.3), size = 90 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> * ETHER Type=9000 (Loopback), size = 60 bytes
pvfs2-io-0-3 -> * ARP C Who is 172.25.30.100, atlas-pvfs2 ?
atlas-pvfs2 -> pvfs2-io-0-3 ARP R 172.25.30.100, atlas-pvfs2 is 0:14:4f:70:ff:17
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
atlas-pvfs2 -> pvfs2-io-0-3 TCP D=111 S=874 Syn Seq=2068043912 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK>
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (TCP port 111 unreachable)
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> * ETHER Type=9000 (Loopback), size = 60 bytes
Server # tshark -i eth1
Running as user "root" and group "root". This could be dangerous.
Capturing on eth1
0.000000 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
0.313739 Cisco_3d:68:10 -> CDP/VTP/DTP/PAgP/UDLD CDP Device ID: MILEVA Port ID: GigabitEthernet1/0/16
2.006422 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
3.483733 172.25.30.100 -> 172.25.30.120 TCP 865 > sunrpc [SYN] Seq=0 Win=49640 Len=0 MSS=1460 WS=0
3.483752 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
4.009741 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
6.014524 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
6.551356 Cisco_3d:68:10 -> Cisco_3d:68:10 LOOP Reply
8.019386 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
8.484344 Dell_70:ad:29 -> SunMicro_70:ff:17 ARP Who has 172.25.30.100? Tell 172.25.30.120
8.484569 SunMicro_70:ff:17 -> Dell_70:ad:29 ARP 172.25.30.100 is at 00:14:4f:70:ff:17
10.024411 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
12.030956 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
12.901333 Cisco_3d:68:10 -> CDP/VTP/DTP/PAgP/UDLD DTP Dynamic Trunking Protocol
12.901421 Cisco_3d:68:10 -> CDP/VTP/DTP/PAgP/UDLD DTP Dynamic Trunking Protocol
^[[A 14.034193 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
15.691119 172.25.30.100 -> 172.25.30.120 TCP 866 > sunrpc [SYN] Seq=0 Win=49640 Len=0 MSS=1460 WS=0
15.691138 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
16.038944 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
16.550760 Cisco_3d:68:10 -> Cisco_3d:68:10 LOOP Reply
18.043886 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
20.050243 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
21.487689 172.25.30.100 -> 172.25.30.120 TCP 867 > sunrpc [SYN] Seq=0 Win=49640 Len=0 MSS=1460 WS=0
21.487700 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
22.053784 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
24.058680 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
26.063406 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
26.558307 Cisco_3d:68:10 -> Cisco_3d:68:10 LOOP Reply
~thank you for any help you can provide!!!

[SOLVED] MPD through mounted NFS Share

Hi all. I am using MPD paired with Ncmpcpp, and in my configuration (for both mpd & ncmpcpp) I have the music directory set to /mnt/Shares/Music which is where I am mounting a NFS share located on the local network.
However ncmpcpp seems to be only partially reading the directory. In the server directory I have two subdirectories (mp3 and ogg) but my music player seems to only be reading the mp3 directory. I have tried updating the database through ncmpcpp, restarting the computer, restarting mpd through systemctl, and even tried using symlinks within the directory (and having "follow internal" and "follow external" symlinks set to "yes" in /etc/mpd.conf).
None of these seem to work in making mpd read the ogg directory.
Edit: Mounting through NFS automatically chowns the share to the local user, so not only did I have to sudo chown -R <user>:users the music share directory on the host I also had to reconfigure my MPD settings to run as a local user as well in order to have proper permissions for the NFS share. Prior to that it was running system wide as the MPD user. This has solved the problem completely.
Last edited by felixculpa (2012-12-26 05:24:19)

WonderWoofy wrote:
Awesome, don't forget to mark your thread as [Solved] by editing your first posts. Sorry I couldn't have been of better help to you. Glad you solved it though.
Edit: I did think it kind of odd (and unlikely) that ogg would not be an automatically supported format, but the source told me otherwise... strange.
Thanks. The Arch community is awesome and I appreciate the help I get in the forums. I am currently updating the database but it is taking quiet some time, so I am not 100% I have fixed the problem. After it is done, and if it works I will update the thread as [Solved].
Thanks again.
Edit: I forgot to mention that I was mistaken in the not reading ogg files part. It was reading only some files from both directories; it just wasn't reading the files it didn't have permission for I'm guessing.
Last edited by felixculpa (2012-12-26 03:47:46)

[SOLVED]Can´t mount nfs shares!

Hello,
I am trying to get up a fileserver. I installed an old PC with Arch and configerd it over SSH. I followed the wiki over NFS and NFSv4. But everytime I want to mount a share that is in the physical map /home/jozef/shares/downloads, I get the following error:
mount.nfs4: timeout set for Mon Aug 24 14:36:57 2009
mount.nfs4: text-based options: 'clientaddr=192.168.0.100,addr=192.168.0.111'
mount.nfs4: mount(2): Permission denied mount.nfs4: access denied by server while mounting 192.168.0.111:/shares/downloads
I tried to mount it with the following command:
mount -v -t nfs4 192.168.0.111:/shares/downloads /media/Downloads-Server
Lets call the fileserver fileserver and my workstation Gamepc. Here I will give you some files that I think are needed, from fileserver and Gamepc are there other files you need, I will post them.
/etc/exports on fileserver
# /etc/exports
# List of directories exported to NFS clients. See exports(5).
# Use exportfs -arv to reread.
# Example for NFSv2 and NFSv3:
# /srv/home hostname1(rw,sync) hostname2(ro,sync)
# Example for NFSv4:
# /srv/nfs4 hostname1(rw,sync,fsid=0)
# /srv/nfs4/home hostname1(rw,sync,nohide)
# Using Kerberos and integrity checking:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/home gss/krb5i(rw,sync,nohide)
/shares 192.168.0.12(rw,fsid=0,no_subtree_check,async,no_root_squash)
/shares/downloads 192.168.0.12(rw,no_subtree_check,async,no_root_squash,nohide)
/etc/hosts.allow on fileserver
# /etc/hosts.allow
sshd: 192.168.0.0/255.255.255.0
#nfsd: 192.168.0.0/255.255.255.255
#portmap: 192.168.0.0/255.255.255.255
#mountd: 192.168.0.0/255.255.255.255
nfsd: ALL
portmap: ALL
mountd: ALL
# End of file
/etc/hosts.deny on fileserver
# /etc/hosts.deny
ALL: ALL: DENY
# End of file
/etc/conf.d/nfs-common on fileserver
STATD_OPTS="--no-notify"
/etc/conf.d/nfs-server on fileserver
STATD_OPTS="--no-notify"
/etc/rc.conf on fileserver
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK=""
USEDIRECTISA="no"
TIMEZONE=""
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="myhost"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="dhcp"
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network rpcbind nfs-common nfs-server netfs crond !xinetd !samba sshd transmissiond)
/etc/rc.conf on Gamepc
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Europe/Amsterdam"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="GAMEPC"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="dhcp"
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network rpcbind nfs-common @netfs crond @hal @fam @samba @alsa @cups)
/etc/hosts.allow on Gamepc
# /etc/hosts.allow
sshd:ALL
# End of file
/etc/hosts.deny on Gamepc
# /etc/hosts.deny
ALL: ALL: DENY
# End of file
If someone could help me, I would be pleased.
With kind regards,
Jozef00
Last edited by jozef00 (2009-09-01 15:28:07)

Are you sure that the nfs module is loaded? Do
lsmod | grep nfs
to check. If "nfs" doesn't appear then that's your problem. Do:
sudo modprobe nfs
and continue.
EDIT: Also, I'll assume both your server and your client machine are connected to the network. You have the network DAEMON "!"-disabled in each machine's /etc/rc.conf. So I'm assuming you're connecting them to the network in some other way, and have verified that you can, for example, ssh from one machine to the other.
Third, you're sure that /share exists on your server machine, that a (presumably empty) directory /share/downloads exists inside it, that another folder is mounted on top of that empty directory? When you type "mount" on the server machine there should be a line containing "on /share/downloads".
Fourth, if your client's ip address is 192.168.0.100 (this will be displayed when you do "ifconfig") then the /etc/exports on your server has been changed to read:
/shares 192.168.0.100(rw,fsid=0,no_subtree_check,async,no_root_squash)
/shares/downloads 192.168.0.100(rw,no_subtree_check,async,no_root_squash,nohide)
Then you either typed "exportfs -rf" on the server, or stopped and restarted nfs-server. (I'd stop nfs-server, nfs-common, and rpcbind, then start them up again in reverse order, to be sure.)
STATD_OPTS has no effect in /etc/conf.d/nfs-server. Also, you don't need to use statd if you're using nfs4. So you could change /etc/conf.d/nfs-common to read:
NEED_STATD=no
NEED_IDMAPD=yes
and /etc/conf.d/server and can be blank.
(Then restart everything, as described above.)
If you're using the latest arch packages then portmap has been replaced by rpcbind (which you do have in your DAEMONS line on the server). So you need to change the "portmap:" line in your server's /etc/hosts.allow to "rpcbind:". I also have a "lockd:" line in my /etc/hosts.allow, in addition to what you have. It's probably not the source of your present troubles, and I'm not sure it's necessary. But you could try adding it.
Finally, did you add/change a "Domain = ..." line in the /etc/idmapd.conf on your server, and a corrsponding line in the /etc/idmapd.conf on your client?
Last edited by Profjim (2009-08-25 12:51:48)

Cannot mount NFS shares using the Finder

Hello all!
I have a directory structure on a OpenSuse NFS Server which I like to browse/read using my MAC OSX 10.5.6. It works like a joy when I am mounting the NFS share on the command line using "sudo":
sudo mount -o resvport nfshost:/full/path/NFS/share /My/mount/point
However, this is kind of unconvenient as I need to start Terminal and sudo always asks me for the root password. I would appreciate to mount the NFS share just as I mount afp shares using the Finder. But the NFS share is neither searchable using the Finder nor does it show up in the list of host in the side bar of the Finder.
Does anyone has an idea how to solve that? Thx for your information!

The problem is most likely that your NFS server requires that connections come from reserved ports but you can't connect that way from the Finder GUI.
Your example:
sudo mount -o resvport nfshost:/full/path/NFS/share /My/mount/point
shows that you need to use "-o resvport" and that you need to do the mount as root. (This is because the networking stack requires you to be root to get a reserved port.) When you try to mount it via the Finder, you can't specify any mount options like "-o resvport" and even if you could the mount would fail because the Finder isn't running as root.
My first suggestion would be to change the configuration of your server to not require clients to use reserved ports for the NFS protocol. Unfortunately, Linux chooses to call that option "insecure" even though requiring the use of reserved ports (using "secure") doesn't actually make NFS more secure.
Alternatively, you could configure the mount to be performed by something that does do the mount as root - e.g. automount/autofs. You can do this by configuring the mount on Directory Utility's "Mounts" section... you'll want to add "resvport" to the "Advanced mount options" field.
HTH
--macko

Thunar freezing when mounting NFS shares

I have used Thunar and NFS for some time without any problems, but in the past week Thunar has been locking up solid when I use it to access a NFS share for more than a minutes or so. It totally locks up the Thunar GUI and I have to force it to quit. When this happens I noticed that the rpc.mountd process becomes zombified or defunct, and AutoFS no longer works too. Restarting these processes with systemctl does not work, since the restart command just hangs.
I run "journalctl -xn" when this happens, but noting really stands out.
I don't have any issues when I access the same NFS share using a terminal.
Currently I have a less than satisfactory workaround - which is to use PCmanFM instead of Thunar. PCmanFM seems to have the good graces to just automatically crash after mounting a NFS share for more than a minute and thus not case all the problems with rpc.mountd & AutoFS.

I finally solved my problem by changing the mount options to this in fstab:
pc-francois.local:/francois /mnt/pc-francois nfs4 rw,proto=tcp,vers=4.0,noauto,users,intr 0 0
One week to find it... Maybe it wants to use nfs 4.1 by default.

Windows 2012 R2 - Access problems to NFS shares via IPv6

Hello,
we setup some NFS shares on HNAS storage box. The connection to this storage is only possible over IPv6 network.
My server with Windows 2012 R2 has the feature 'Client for NFS' installed and a 'showmount -e servername/or IPv6 address' works. I can see all shares when i try to open the storagebox in Windows Explorer with the command "\\servername" or "\\IPv6
address", too.
My problem is, when I try to mount the share via "Map network drive" or "mount \\servername\sharename *" I get Error 53 - Network path not found.
The share is configured that every server in the IPv6 subnet could access it and it works on Unix machines, but not on Windows.
It does not matter if i set some option parameters for the "mount" command like sec=sys or anon, everytime error 53.
I don't know, if the share needs special options for Windows. I hope somebody can help.
Kind regards

Hi,
here is the output of your 2 commands:
PS C:\Users\admin> get-SmbConnection
PS C:\Users\admin> get-SmbServerConfiguration
AnnounceServer                  : False
AsynchronousCredits             : 64
AutoShareServer                 : True
AutoShareWorkstation            : True
CachedOpenLimit                 : 0
AnnounceComment                 :
EnableDownlevelTimewarp         : False
EnableLeasing                   : True
EnableMultiChannel              : True
EnableStrictNameChecking        : True
AutoDisconnectTimeout           : 0
DurableHandleV2TimeoutInSeconds : 30
EnableAuthenticateUserSharing   : False
EnableForcedLogoff              : True
EnableOplocks                   : True
EnableSecuritySignature         : True
ServerHidden                    : True
IrpStackSize                    : 15
KeepAliveTime                   : 2
MaxChannelPerSession            : 32
MaxMpxCount                     : 50
MaxSessionPerConnection         : 16384
MaxThreadsPerQueue              : 20
MaxWorkItems                    : 1
NullSessionPipes                : HydraLsPipe
NullSessionShares               :
OplockBreakWait                 : 35
PendingClientTimeoutInSeconds   : 120
RequireSecuritySignature        : False
EnableSMB1Protocol              : True
EnableSMB2Protocol              : False
Smb2CreditsMax                  : 2048
Smb2CreditsMin                  : 128
SmbServerNameHardeningLevel     : 0
TreatHostAsStableStorage        : False
ValidateAliasNotCircular        : True
ValidateShareScope              : True
ValidateShareScopeNotAliased    : True
ValidateTargetName              : True
EncryptData                     : False
RejectUnencryptedAccess         : True
I try to access the file share with Windows Explorer. When I enter \\fe08--babe-face-cafe-dead.ipv6-literal.net (just example), I can see all shares on the storage box. When I double-click the share, I want to access, where an access is definitely allowed,
it takes a while and then the error "\\fe08--babe-face-cafe-dead.ipv6-literal.net\share is not accessable. You might not have permission to use this network resource. ..." appears. Of this action a recorded the trace.
Another way I tried is to open command line an type "mount \\fe08--babe-face-cafe-dead.ipv6-literal.net\share *". After this an error 53 occurs immediately without any wait time.

Error mounting NFS share - mount.nfs: Operation not permitted

I've got an NFS share on a FreeBSD server which I mount via fstab.
It mounts automatically at boot and everything is fine.
However, if I unmount it and try to mount it again I get:
mount.nfs: Operation not permitted
I have tried vers=3 and nfsvers=3 in fstab, but to no avail.
rpcbind is allowed in /etc/hosts.allow.
Does anyone have any ideas?
fstab entry:
server:/path/to/files /mnt/files nfs ro,hard,intr,nfsvers=3 0 0

Tagging along, I have the same problem, although I have a different setup:
- Server = Arch linux
- Client1 = Debian Testing linux
- Client2 = Arch linux
On client1, I'm unable to mount all NFS-shares. 2 out of 3 mount ok and the third fails with this error (both through fstab and manually):
# mount -a
mount.nfs4: access denied by server while mounting (null)
On Client2 I'm able to connect automatically and manually to all shares.
Maybe it is Debian-related, but the debian user forums have not been of much help...
THX for any input!
Last edited by zenlord (2010-03-04 12:07:04)

First access to mounted NFS share very slow in finder

Hi,
we have some NFS Shares on our Celerra Fileserver mounted by Mac running Snow Leopard 10.6.2 (just updating to 10.6.3).
After a mount of FS in finder, there are approx 600MB loaded from the share on first access. On our LAN it isn't that problem ... but off-site it's very annoying if that amount of data have to go through an small 1Mbit pipe.
Access via Terminal to the same directory doesn't have the problem. Spotlight is disabled with a .metadataneverindex on the root of the share.
Now my question :
Is there any kind of cache, which can be turned of to prevent finder from loading the whole structure / part of files on first access ?
Thanks,
Robert

Thanks for your reply peter.
I have tried , without connecting database, i just hardcoded data values then i tried to access my application at that time it was very fast.
Then i came to conclusion that problem is in some where in data base connection. because my query is also fine tunes.

"Network Error - 53" while trying to mount NFS share in Windows Server 2008 client

CentOS | Windows 2008
I've got a CentOS 5.5 server running nfsd. On the Windows side, I'm running Windows Server 2008 R2 Enterprise. I have the "Files Services" server role enabled and both Client for NFS and Server for NFS are on.
I'm able to successfully connect/mount to the CentOS NFS share from other linux systems but am experiencing errors connecting to it from Windows. When I try to connect, I get the following:
C:\Users\fooadmin>mount -o anon 10.10.10.10:/share/ z:
Network Error - 53
Type 'NET HELPMSG 53' for more information.
(IP and share name have been changed to protect the innocent :-) )
Additional information:
I've verified low-level network connectivity between the Windows client and the NFS server with telnet (to the NFS on TCP/2049) so I know the port is open. I've further confirmed that inbound and outbound firewall ports are present and enabled.
I came across a
Microsoft tech note that suggested changing the "Provider Order" so "NFS Network" is above other items like Microsoft Windows Network. I changed this and restarted the NFS client - no luck.
I've confirmed that the share folder on the NFS server is readable/writable by all (777)
I've tried other variations of the mount command like: mount 10.10.10.10:/share/ z: and
mount 10.10.10.10:/share z: and mount -o anon mtype=hard \\10.10.10.10:/share * No luck.
As per the command output, I tried typing NET HELPMSG 53 but that doesn't tell me much. Just "The network path was not found".
I'm lost on how to proceed with troubleshooting. Any ideas?

There are usully two aspect that come to mind:
1. Syntax of mount command
2. Mismatch of NFS versions
Third reason is here
http://blogs.technet.com/b/sfu/archive/2011/11/21/getting-network-error-53-network-path-not-found-quot.aspx
Rgds
Milos

Can't mount NFS share via GUI

Mac OS X 10.8.2
MacBookPro5,3
Hello,
I've recently upgraded to OS X 10.8.2 and am having great difficulty in mounting my NFS shares via the OSX GUI. This worked fine at OS X 10.6.
My aim is to provide an automount type of setup so that less experienced users don't have to worry about the command line.
Can someone please point me in the right direction here?
This is what I've tried to date.
My NFS service is hosted on my Debian server. It supports NFS v4. The service is working and stable and is used routinely with Ubuntu clients. It has also worked with OS X 10.6 clients in the past, but not with OS X 10.7 clients.
To date I have tried the following options:
Mount via finder: Connect to server option using syntax: nfs://<user>@<server>/<share>
setting up autofs using the instructions from pmbuko
using the command line to mount the share.
The first option failed repeatedly. I did find that it would eventually work, though only after I'd manually mounted the share at the command line.
I have not been able to get the second option to work.
I initiate autofs using the command 'automount -vc' and see that the connection is recognised
when I attempt to cd into a directory below the mount point, I eventually get the message 'Connection Refused'.
when I check my Debian logs, I find that the NFS service had actually received an authenticated mount request from the Mac.
when I check my Mac Console logs, I see an error:kernel: nfs_connect: socket error 61 for <server>/<share>
I was able to get the third option working, but only after using the '-o resvport' option.
'Something' does appear to be broken with OS X 10.8.2 as an NFS client.
Any thoughts?

I have found a work around that meets my imediate needs, though it doesn't allow me to use autofs functionality.
The work around uses the traditional Unix/Linux approach of automatically mounting a file system or NFS share via fstab at boot time. OS X 10.8 still supports fstab, even though the file is not included in the default installation.
Once mounted, the NFS share appears as if it is part of the normal file system.
The following is only intended for people confident in Unix or Linux systems administration and in using a shell environment via the command line. Do not attempt this if you do not have these skills.
To set up for fstab, do the following within a terminal session:
create an empty directory in your file system that you can use as your mount point for your NFS share:
sudo mkdir /data/share
sudo chown root:wheel /data/share
using your favourite editor, create the fstab file (in a terminal type 'man fstab' for details)
sudo vi /etc/fstab
add similar to the following to /etc/fstab and then save and exit, substituting your own values where appropriate
# My NFS share
<your-server>:/<your-share> /data/share nfs resvport,rw,hard,intr 0 0
sudo chown root:wheel /etc/fstab
Please note: you may not need the resvport option in the fstab line above. It will depend on your NFS server's requirements.
Once you have done this, reboot your Mac and your NFS share should be mounted at the mount point that you defined.
If not, check your logs to see what went wrong.

Can not mount nfs shares

I have a centos server which tries to mount a nfs share from an osx server tiger.
on the osx server showmount -e shows me the mountpoint perfectly.
on the linux server i try to mount the mountpoint and after some time it gives me the error:
mount.nfs: Input/output error
does this sound familiar to anyone? please help me :P

more information:
nidump -r /exports .
"name" = ( "exports" );
CHILDREN = (
"clients" = ( "192.168.0.10" );
"name" = ( "/backup" );
"opts" = ( "" );
showmount -a returns:
Exports list on localhost:
/backup 192.168.0.10

Can't create or mount NFS share

I am trying to create an NFS share on a server that already does quite nicely sharing AFP and SMB. A friend tells me that this is easy but I can't make it work, I'm still told that my password is incorrect.
Can you watch this short movie to see what I'm doing and advise what I'm doing wrong?
Thank you in advance.

I am trying to create an NFS share on a server that already does quite nicely sharing AFP and SMB. A friend tells me that this is easy but I can't make it work, I'm still told that my password is incorrect.
Can you watch this short movie to see what I'm doing and advise what I'm doing wrong?
Thank you in advance.

[SOLVED] Problem mounting nfs shares

Similar Messages

Maybe you are looking for