Arch Linux

cmays90

Member

Registered: 2009-12-18

Posts: 31

mount.nfs: Argument list too long (NFS problem)

I just finished installing and following the guide to set up NFS for my desktop (server) and my laptop (client).  I believe I have everything configured correctly but every time I try to mount the server file, I get this error: mount.nfs: Argument list too long.  None of the doc and man pages that I found say anything about this particualr error.  Google wants me to believe its a problem/limitation with bash as opposed to an issue with my config, but I am not quite so convinced.

The command I am running to mount is

mount 192.168.1.100:/nfs /nfs

Both machines have a /nfs folder, and on both machines that folder is universally rwx.  My server is sitting at 192.168.1.100 and my laptop is at 192.168.1.101. The /etc/exports is posted below.

# /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)
#

/nfs 192.168.1.101(rw,sync,no_root_squash,subtree_check)

I have also changed the hosts.allow files on both machines to handle the new daemons, which seem to be running correctly, as I do not have any errors or warnings from them.  That is all I can think to provide right now.  If I am missing anything, please feel free to let me know, and I will provide it ASAP.

cmays90

Member

Registered: 2009-12-18

Posts: 31

Re: mount.nfs: Argument list too long (NFS problem)

I messed around with some of the settings (I figured this was a client based problem) and eventually decided to tell mount to be a bit more explicit in what it was doing......

mount -t nfs4 192.168.1.100:/nfs /nfs

This led to a different error:

mount.nfs4: mounting 192.168.1.100:/nfs failed, reason given by server:
  No such file or directory

This seemed server based (duh), so I changed my exports file to look something more like

/nfs *(rw,fsid=0,sync,no_root_squash,subtree_check)

That supposedly makes /nfs equivilant to a root directory, so when mounting the new command becomes

mount -t nfs4 192.168.1.100:/ /nfs

And it worked.  Now using the hard drive of my desktop and the solid state drive of my laptop.  Best of all worlds