Softpanorama
(slightly skeptical) Open Source Software Educational Society

May the source be with you, but remember the KISS principle ;-)

Google   


The /etc/vfstab File

The /etc/vfstab file, referred to as the file system table, specifies resources that should be automatically mounted when the system is booted or when the mountall command is used.

This file can be modified using any text editor. To automatically mount an NFS resource, add a line to the /etc/vfstab file that contains the appropriate options that would have been entered manually with a mount -F nfs command. To remove automatic mounting of an NFS resource, delete the appropriate line from the /etc/vfstab file.

NFS supports client-side failover. That is, if an NFS resource becomes unavailable, the client can switch to another NFS server that provides a "replicated" copy of the resource. This failover capability can be enabled by adding an entry in the /etc/vfstab for the resource. In the Device to Mount field, list the systems that provide the replicated resource separated by commas. Also, the read-only option (-o ro) is specified in the Mount Options field. For example, to provide client-side failover for the /export/local resource that is available from either the "alpha" or the "beta" NFS servers and mounted at /usr/local, add the following entry to the /etc/vfstab file:

alpha,beta:/export/local - /usr/local nfs - no -o ro


Note that read-only resources (-o ro mount option) can be configured for client-side failover. Also be certain that the system names are valid and separated by commas.


Copyright © 1996-2008 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. Submit comments This document is an industrial compilation designed and created exclusively for educational use and is placed under the copyright of the Open Content License(OPL). Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

Standard disclaimer: The statements, views and opinions presented on this web page are those of the author and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

Last modified: February 28, 2008