Mounting NFS Shares

**OctAvio2011** · 10-09-2010

I have a small question about the management of NFS: I want to mount a drive using NFS on a remote server (mach). I get always an error. The command "mount-a"(in fstab with" mach: / home / thales / home / thales nfs exec, dev, suid, rw, bg, nfsvers = 2 1 1 ") look back. NFS therefore seem to be working on the server! However, the disc is still mounted. So I check the server "mach" does not think the installation works by typing "showmount-a mach | grep vb_asz(vb_asz = name of my machine). Please help.

**Eric B** · 10-09-2010

We prefer to use an auto-installer: it will mount the partitions on demand and unmount when they are no longer used.

1. We install the automounter:

Code:

$ Sudo aptitude install autofs

2. It indicates that / net is a point managed by autofs automounter, and is managed through the script / etc / auto.net is provided by the package autofs :

Code:

# Extract the file / etc / auto.master
      # / Net is a directory managed by autofs
      # - each sub-directory / net will run through the script / etc / auto.net
      # - dismantling after fifteen minutes of non-use.
      / net / etc / auto.net - timeout = 900

3. Restarting the service autofs :

Code:

$ Sudo invoke-rc.d autofs restart

**Glenny** · 10-09-2010

If the server nfs.xx.auf.org sharing a directory / home, the assembly will be done in / net / nfs.xx.auf.org / home. A common technique is to make a symbolic link from / home to / net / nfs.xx.auf.org / home for everything so transparent to users. You need to know the directories shared by the server nfs.xx.auf.org, the script auto.net runs the command showmount-e nfs.xx.auf.org. The mount options are set "hard" in the script, look at them. You can run a showmount to verify that the fixtures are clearly visible, for example:

* t

Code:

homas @ pc: ~ $ showmount-e nfs.refer.sn
      Export list for nfs.refer.sn:
      / home 10.196.0.0/20, 192.168.0.0/16
      / home2 10.196.0.0/20, 192.168.0.0/16

**JonathanD** · 10-09-2010

you need to check that automount is it really active (and I do not speak if you are not using automount in your CNF). The showmount-e nfs.xx.auf.org returns he familiar with the list of all directories exported by the server? Check exports, seen from the client side:

Code:

# Showmount-e-a-nfs server
export list for nfs:
/ home 10.196.0.0/20, 192.168.0.0/16
/ home2 10.196.0.0/20, 192.168.0.0/16

# That gives direct access to the directory automount command line? For example:

Code:

$ Cd / net / nfs.xx.auf.org / home

# Check if the directory appears, although it possesses the rights and owners expected:

Code:

$ Ls-lsd / net / nfs.xx.auf.org / home

**Macarenas** · 10-09-2010

On RedHat, most system configuration files are already located in / etc / sysconfig. We will move then just those who are not and add symlinks. Then we assemble a directory / etc / sysconfig per station. C ' is the only part that is specific to the distribution used here. With other distributions, simply create a sysconfig directory, move all the configuration files that can be shared, and add the necessary links. Similarly, / etc / rc.d/rc3.d (or equivalent in other distros) can be differences between the server and stations. If we consider that all stations are launching similar services.

**Sindu** · 14-09-2010

NFS allows a computer to access a file system that resides on disk (or disks: there may be many) to another computer if the file system was mounted locally. The NFS server is the computer that the disk is physically attached. The computers that use the file system is called remote NFS clients. Before that NFS clients can mount, that is to say, importing a file system residing on the NFS server's disk, it is the export.