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.

Similar Messages

  • [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)

  • 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

  • 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".

  • 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.

  • 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.

  • IVPN on non OSX Server, can't mount volumes remotely via VPN

    I recently got iPVN to create a VPN to my home network. My router simply couldn't be used as an end-point.
    I have successfully installed it, and it does allow me to connect to my home network remotely. The problem is, whenever I try to mount a volume from a machine within my home network, I am prompted for a userid/password. My userid/password doesn't work.
    Setup:
    Home network using private Class C (192.168.1.x). 2009 MacMini is VPN server, and address is manually assigned for this machine (other machines within home network use router as DHCP server). I have forwarded ports 1701, 4500 and 500 (per iVPN instructions) for an L2TP VPN. UDP packets only, and all of these ports are forwarded to the MacMini and it's manually assigned address. My router is configured to use DynDNS if it's address changes, and that works successfully as well (using other services directly to the same MacMini, etc. that DO NOT rely on the VPN).
    I can successfully connect to the VPN, and ping machines within the home network successfully. However, I do not see any of the machines via Bonjour (I understand this is an issue with Bonjour and generally all VPNs). So, once connected to the VPN, I try to mount a volume that is shared on the MacMini. I can do this with either form:
    afp://192.168.1.x/<volumename> or afp://<machinename>/<volumename> (after setting machine name up in /etc/hosts).
    I'm fairly certain I'm getting through, and a mount is attempted, and asks for a userid/password. Same as normal. However, entering my username/password won't let me mount the drive. I keep getting errors indicating the username/password is incorrect, which I know is not the case.
    I have tried this with the MacMini firewall on (allowing shared service), and I have tried it with the MacMini firewall off.
    What am I missing here? Some additional port that should be forwarded? Open it up for TCP as well as UDP?

    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.

  • CIFS Kernel Module Needed for A7600-F. Can't mount CIFS Shares.

    Does anyone have, or could compile a CIFS Kernel for the A10 (A7600-F) please.
    I am trying to mount CIFS shares on my NAS, nut don't have the cifs.ko file required.
    Help would be greatly appreciated.
    Thanks.
    Model Number: Levono A7600-F
    Android Version 4.4.2
    Kernel Version: 3.4.67
    Build Number: A7600F_A442_000_022_140829_ROW
    The tablet was rooted using Kingo Root.

    Hi Gmarkall,
    You really seem to know what you're doing.
    I need the same module files for my A10-70 (A7600-F).
    Are you able to complie these please?
    Lenovo make the source code available here
    http://support.lenovo.com/gb/en/products/tablets/a​-series/a10-70-tablet?TabName=Downloads
    I've tried to do this myself, but can't figure it out.
    Can you help me please?
    Thanks
    Moderator comment: This post and its replies below were pulled out of an old thread about a different model and merged here. Subjects here and below edited to match. Was: Re: CIFS Kernel Module? - can't mount CIFS share on IdeaPad A2109

  • 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.

  • 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

  • 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.

  • Can't mount NFS from my Arch laptop, am I missing something obvious?

    Hello,
    I have been trying to solve this issue for over a week and tried everything that I can imagine with no luck...
    Set up:
    - Qnap SS-839 Pro with several NFS shares on
    /share/to_sort
    /share/movies
    /share/music
    etc.
    - MythTV frontend/backend running Mythbuntu.
    I can mount my NFS shares without problem. I use this fstab.
    192.168.1.100:/share/Music /var/lib/mythtv/music nfs nolock,async,proto=tcp,rw,ac 0 0
    192.168.1.100:/share/Videos /var/lib/mythtv/videos nfs nolock,async,proto=tcp,rw,ac 0 0
    - Arch laptop
    I can't get to mount any of the NFS share:
    [18:59:14][[email protected]]
    /mnt/aether Arch64# /etc/rc.d/rpcbind restart
    :: Stopping rpcbind                                                      [DONE]
    :: Starting rpcbind                                                      [DONE]
    [18:59:32][[email protected]]
    /mnt/aether Arch64# mount 192.168.1.100:/share/to_sort/ to_sort/
    mount.nfs: rpc.statd is not running but is required for remote locking.
    mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
    mount.nfs: an incorrect mount option was specified
    [19:00:03][[email protected]]
    /mnt/aether Arch64# mount 192.168.1.100:/share/to_sort/ to_sort/ -o no-lock
    mount.nfs: an incorrect mount option was specified
    I tried using the 2 following lines in my fstab on  my laptop but nothing works:
    1) 192.168.1.100:/share/to_sort /mnt/aether/to_sort nfs nolock,async,proto=tcp,rw,ac 0 0  (same option than under mythbuntu)
    2) 192.168.1.100:/share/to_sort /mnt/aether/to_sort nfs defaults 0 0
    I'm no guru when it comes to nfs sharing etc, but I really can't see what I am missing here, nor whatelse can I try!
    Any idea will be more than welcome!
    Thanks in advance
    Ludo

    I finally solved this problem after 4 months after someone posted a similar issue with Arch few days ago...
    He said to install the iana-etc package... I already had the package but still gave it a go:
    [08:15:33][[email protected]]
    ~ Arch64$ showmount -e 192.168.0.100
    clnt_create: RPC: Unknown host
    [08:15:41][[email protected]]
    ~ Arch64$ sudo pacman -Syu iana-etc
    Password:
    :: Synchronising package databases...
    core is up to date
    extra is up to date
    community is up to date
    archlinuxfr is up to date
    warning: iana-etc-2.30-1 is up to date -- reinstalling
    :: Starting full system upgrade...
    resolving dependencies...
    looking for inter-conflicts...
    Targets (1): iana-etc-2.30-1
    Total Download Size: 0.00 MB
    Total Installed Size: 0.88 MB
    Proceed with installation? [Y/n]
    (1/1) checking package integrity [########################################################################################################################] 100%
    (1/1) checking for file conflicts [########################################################################################################################] 100%
    (1/1) upgrading iana-etc [########################################################################################################################] 100%
    [08:20:13][[email protected]]
    ~ Arch64$ showmount -e 192.168.0.100
    Export list for 192.168.0.100:
    /to_sort
    /mythbox
    /Qweb
    /Qusb
    /Documents
    [08:20:18][[email protected]]
    ~ Arch64$
    As you can see, it is now working and I am now completely puzzled...
    How come reinstalling this package solved the issue?
    Any idea on what the problem was would be more than welcome
    Thanks

  • Can't mount NFS exports on Arch laptop

    I've browsed the forums, double checked the wiki, but for some reason I'm not able to mount my NFS exports. There must be some small issue not letting me do this, but I can't find it. This is my /etc/exports file on the server (desktop):
    /glados 192.168.0.99(rw,fsid=0,no_subtree_check)
    /glados/movies 192.168.0.99(rw,no_subtree_check)
    And the order of the rc.conf daemons on the server:
    DAEMONS=(syslog-ng dbus network @netfs crond rpcbind nfs-common nfs-server !hwclock ntpd)
    On the client (laptop):
    DAEMONS=(syslog-ng dbus network crond @bumblebeed @networkmanager @postgresql rpcbind nfs-common nfs-server sshd)
    $ showmount -e 192.168.1.101
    Export list for 192.168.1.101:
    /glados/movies 192.168.0.99
    /glados 192.168.0.99
    Now try mount:
    $ sudo mount -t nfs4 192.168.1.101:/movies server/
    Here it just freezes and nothing happens. I also did the configuration both on server and client side of /etc/idmapd.conf, adding a domain.
    Nothing happens on the client side when I try to mount. It just freezes there. Both machines running up to date ArchLinux.
    Any help is appreciated!
    Last edited by fbt (2012-09-18 03:47:46)

    I just thought that server/ was a typo
    He's able to use showmount -e 192.168.1.101 from the machine with the ip 192.168.0.99 so assumed his network's functioning ok ... but you know what they say about 'assume', which machine did you actually run the showmount command on?  This might be stating the obvious, but if you ran it on 192.168.0.101 make sure 192.168.0.99 and 192.168.1.101 are communicating with each other
    Also I think you're not mounting the path correctly, you have movies exported as: 
    /glados/movies 192.168.0.99(rw,no_subtree_check)
    But you're trying to mount it as:
    sudo mount -t nfs4 192.168.1.101:/movies server/
    Try mounting it something like this: 
    sudo mount -t nfs4 192.168.1.101:/glados/movies /server/movies
    That command is assuming you're wanting to put your nfs shares inside a folder called /server, also be aware that the directory you're trying to mount your shares inside of has to already exist
    Incidentally, why are you mounting /glados and then also mounting directories unger /glados such as /glados/movies, by mounting /glados as an nfs share you already have access to /glados/movies.  Once /glados is mounted then you can symlink to or bind mount any directories under it to any location you want

  • 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)

  • 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.

Maybe you are looking for