Sponsored Content
Full Discussion: NFS automount on reboot
Operating Systems AIX NFS automount on reboot Post 302900988 by paakofi on Friday 9th of May 2014 08:26:39 PM
Old 05-09-2014
This is how it looks like. I used smitty nfs to mount the nfs directory.

Code:
/local:
        dev             = "/dev/mount"
        vfs             = nfs
        nodename        = *****.com
        mount           = true
        options         = bg,soft,intr,vers=3,nosuid,sec=sys
        account         = false


Last edited by Don Cragun; 05-09-2014 at 09:30 PM.. Reason: Add CODE tags.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Automount

My site has a few sun solaris server including out NIS server and NFS server on solaris machines. we also have few suse linux and redhat linux machine. All our home directory is on our NFS server(sun Solaris) and this is automounted through /etc/auto_master and /etc/auto_home this worked fine... (1 Reply)
Discussion started by: hassan2
1 Replies

2. Solaris

different between soft reboot and hard reboot

Hi Guru's Can any want here could explain to me the different between soft reboot and hard reboot . Best Regards Seelan (3 Replies)
Discussion started by: seelan3
3 Replies

3. Solaris

NFS write error on host : Stale NFS file handle

:confused:Hi all When i see in the /var/adm/messages, i saw the following error unix: NFS write error on host : Stale NFS file handle. unix: (file handle: 45ca415 3e7 a0000 2c7f6 3ebfc25f a0000 2 3e49) It is using sunOS 5.7. Is anybody know what is this error? Is is related to any network... (2 Replies)
Discussion started by: AirWalker83
2 Replies

4. Filesystems, Disks and Memory

Local NFS import / re-export using automount?

Hi, Can I do the following: On SunOS 5.8 /etc/vfstab: remote-host:/Volumes/webdata - /export/home/webdata nfs - yes rw,vers=3,soft,intr,bg,timeo=600 In /etc/auto_direct: /home/science $HOST:/export/home/webdata/science /home/science-edu ... (2 Replies)
Discussion started by: bloyall
2 Replies

5. Solaris

All dependicies of nfs service is online but nfs is offline

Hi all in my server all nfs dependices are online but nfs client is offline root@BIWAPP1 # svcs -a|grep nfs disabled Sep_05 svc:/network/nfs/server:default online Sep_05 svc:/network/nfs/rquota:default online Sep_05 svc:/network/nfs/mapid:default online ... (9 Replies)
Discussion started by: spandhan
9 Replies

6. Solaris

Solaris 9 as a nfs client -- centos as a nfs server.

Hello, I have a centos as nfs server, its name is centos_A. After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/* But, My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies

7. AIX

NFS files after reboot

i Have a mount point from NAS and i mount it My AIX manually the system get rebooted by its self and it did not get mounted , how can i make it mounted with the system up in automated way ? (1 Reply)
Discussion started by: thecobra151
1 Replies

8. Shell Programming and Scripting

Mount NFS Share On NFS Client via bash script.

I need a help of good people with effective bash script to mount nfs shared, By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people. The scenario as follow: An NFS Client with Daily CRON , running bash script... (4 Replies)
Discussion started by: Brian.t
4 Replies

9. Solaris

NFS write error on host xyz: Stale NFS file handle - Solaris 10

Oct 13 12:19:15 xyz nfs: NFS write error on host xyz: Stale NFS file handle. Oct 13 12:19:15 xyz nfs: (file handle: 68000000 1bc5492e 20000000 377c5e 1ce9395c 720a6203 40000000 bdfb0400) Oct 13 12:19:15 xyz nfs: NFS write error on host zyz: Stale NFS file handle. Oct 13 12:19:15 xyz nfs: ... (5 Replies)
Discussion started by: psychocandy
5 Replies
fstab(5)							File Formats Manual							  fstab(5)

Name
       fstab - file containing static information about known file systems

Description
       The  file  contains  descriptive information about the known file systems.  By convention, is created and maintained as a read-only file by
       the system administrator.  Each file system is described by its own line within The order of these lines and the file systems  they  repre-
       sent is important because and sequentially process in the performance of their tasks.

       The format of each file system description in is as follows:
       spec:file:type:freq:passno:name:options
       The meanings of these fields are:

       spec	 The block special file name of the device on which the file system is located.  It can also be a network name for such as or

       file	 The pathname of the directory on which the file system is mounted.

       type	 How the file system is mounted.  The ways in which a file system can be mounted are:
		 rw - mount the file system read-write
		 ro - mount the file system read only
		 rq - mount the file system read-write with quotas
		 sw - make the special file part of the swap space
		 xx - ignore the entry

       freq	 The frequency (in days) with which the command dumps the rw, ro, and rq file systems.

       passno	 The order in which the command checks the rw, ro, and rq file systems at reboot time.

       name	 The  name  of	the file system type.  File systems can have the following types: ufs -- ULTRIX file system and nfs -- SUN Network
		 file system.

       options	 The options field.  This field contains an arbitrary string meaningful only when mounting file systems with  the  specified  file
		 system type name, such as NFS.  The specific options are described in the reference pages.

       Special	actions  occur for file systems of type sw and rq at system boot time.	File systems of type sw are made part of the swap space by
       the command and disk quotas are automatically processed by the command and then enabled by the command for rq file systems.

Examples
       Here is a sample file:
       /dev/ra0a:/:rw:1:1:ufs::
       /dev/ra1g:/usr:rw:1:2:ufs::
       /@bigvax:/bigvax:rw:0:0:nfs::
       /usr/uws2.0@bigvax:/usr/uws2.0:rw:0:0:nfs:soft,bg,nosuid:
       /usr/dec@bigvax:/usr/dec:rw:0:0:nfs:bg,soft,nosuid:
       /usr/pro/xyz@vax:/usr/pro/xyz:rw:0:0:nfs:bg,soft,intr,nosuid:
       The last three entries in the sample shown use NFS options as described in the reference page.

Restrictions
       The passno field of the root file system should be specified as 1.  Other file systems should have larger values.  File systems on the same
       device  should  have  distinct  passno  fields.	File systems on different devices may have the identical passno fields to allow them to be
       simultaneously checked.

       All field delimiters (:) must exist within each file system description; only the options field may not	be  present.   However,  only  the
       fields spec and type are meaningful to sw file systems and only the type field is meaningful to xx file systems.

       The file system description within should be parsed only through use of the routines.

Files
       File system information file

See Also
       getfsent(3x), dump(8), fsck(8), mount(8), mount(8nfs), mount(8ufs) quotacheck(8), quotaon(8), swapon(8)

																	  fstab(5)
All times are GMT -4. The time now is 08:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy